Device, Method, and Graphical User Interface for Forgoing Generation of Tactile Output for a Multi-Contact Gesture

ABSTRACT

An electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface: detects, on the touch-sensitive surface, a gesture that includes an increase of intensity of a contact above a respective intensity threshold. In response to detecting the gesture: in accordance with a determination that the gesture includes a first number of contacts, the device generates a tactile output on the touch-sensitive surface; and in accordance with a determination that the gesture includes a second number of contacts different from the first number, the device forgoes generating the tactile output on the touch-sensitive surface.

RELATED APPLICATIONS

This application is a continuation of PCT Patent Application Serial No.PCT/US2013/069479, filed on Nov. 11, 2013, entitled “Device, Method, andGraphical User Interface for Forgoing Generation of Tactile Output for aMulti-Contact Gesture,” which claims the benefit of and priority to U.S.Provisional Patent Application Ser. No. 61/778,239, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forForgoing Generation of Tactile Output for a Multi-Contact Gesture;” andU.S. Provisional Patent Application No. 61/747,278, filed Dec. 29, 2012,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback,” whichapplications are incorporated by reference herein in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/778,092, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects;” U.S. Provisional Patent Application Ser. No.61/778,125, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Navigating User Interface Hierarchies;”U.S. Provisional Patent Application Ser. No. 61/778,156, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forManipulating Framed Graphical Objects;” U.S. Provisional PatentApplication Ser. No. 61/778,179, filed on Mar. 12, 2013, entitled“Device, Method, and Graphical User Interface for Scrolling NestedRegions;” U.S. Provisional Patent Application Ser. No. 61/778,171, filedon Mar. 12, 2013, entitled “Device, Method, and Graphical User Interfacefor Displaying Additional Information in Response to a User Contact;”U.S. Provisional Patent Application Ser. No. 61/778,191, filed on Mar.12, 2013, entitled “Device, Method, and Graphical User Interface forDisplaying User Interface Objects Corresponding to an Application;” U.S.Provisional Patent Application Ser. No. 61/778,211, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forFacilitating User Interaction with Controls in a User Interface;” U.S.Provisional Patent Application Ser. No. 61/778,284, filed on Mar. 12,2013, entitled “Device, Method, and Graphical User Interface forProviding Tactile Feedback for Operations Performed in a UserInterface;” U.S. Provisional Patent Application Ser. No. 61/778,287,filed on Mar. 12, 2013, entitled “Device, Method, and Graphical UserInterface for Providing Feedback for Changing Activation States of aUser Interface Object;” U.S. Provisional Patent Application Ser. No.61/778,363, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Transitioning between Touch Input toDisplay Output Relationships;” U.S. Provisional Patent Application Ser.No. 61/778,367, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Moving a User Interface Object Based on anIntensity of a Press Input;” U.S. Provisional Patent Application Ser.No. 61/778,265, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Transitioning between Display States inResponse to a Gesture;” U.S. Provisional Patent Application Ser. No.61/778,373, filed on Mar. 12, 2013, entitled “Device, Method, andGraphical User Interface for Managing Activation of a Control Based onContact Intensity;” U.S. Provisional Patent Application Ser. No.61/778,412, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Displaying Content Associated with aCorresponding Affordance;” U.S. Provisional Patent Application Ser. No.61/778,413, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Selecting User Interface Objects;” U.S.Provisional Patent Application Ser. No. 61/778,414, filed on Mar. 13,2013, entitled “Device, Method, and Graphical User Interface for Movingand Dropping a User Interface Object;” U.S. Provisional PatentApplication Ser. No. 61/778,416, filed on Mar. 13, 2013, entitled“Device, Method, and Graphical User Interface for Determining Whether toScroll or Select Content;” and U.S. Provisional Patent Application Ser.No. 61/778,418, filed on Mar. 13, 2013, entitled “Device, Method, andGraphical User Interface for Switching between User Interfaces,” whichare incorporated herein by reference in their entireties.

This application is also related to the following: U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” and U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices,” which areincorporated herein by reference in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that detect inputs for manipulating userinterfaces.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

Exemplary manipulations include adjusting the position and/or size ofone or more user interface objects or activating buttons or openingfiles/applications represented by user interface objects, as well asassociating metadata with one or more user interface objects orotherwise manipulating user interfaces. Exemplary user interface objectsinclude digital images, video, text, icons, control elements such asbuttons and other graphics. A user will, in some circumstances, need toperform such manipulations on user interface objects in a filemanagement program (e.g., Finder from Apple Inc. of Cupertino, Calif.),an image management application (e.g., Aperture or iPhoto from AppleInc. of Cupertino, Calif.), a digital content (e.g., videos and music)management application (e.g., iTunes from Apple Inc. of Cupertino,Calif.), a drawing application, a presentation application (e.g.,Keynote from Apple Inc. of Cupertino, Calif.), a word processingapplication (e.g., Pages from Apple Inc. of Cupertino, Calif.), awebsite creation application (e.g., iWeb from Apple Inc. of Cupertino,Calif.), a disk authoring application (e.g., iDVD from Apple Inc. ofCupertino, Calif.), or a spreadsheet application (e.g., Numbers fromApple Inc. of Cupertino, Calif.).

But existing methods for performing these manipulations are cumbersomeand inefficient. In addition, existing methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for electronic devices with faster, moreefficient methods and interfaces for manipulating user interfaces. Suchmethods and interfaces optionally complement or replace conventionalmethods for manipulating user interfaces. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methods andinterfaces conserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

There is a need for electronic devices with more efficient methods andinterfaces for providing feedback when a focus selector moves over auser interface object. Such methods and interfaces may complement orreplace conventional methods for providing feedback when a focusselector moves over a user interface object. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface. The methodincludes: displaying, on the display, a plurality of user interfaceobjects, where each of the plurality of user interface objects includesa plurality of subdivisions. The method further includes, detectingmovement of a contact on the touch-sensitive surface that corresponds tomovement of a focus selector over a respective user interface object inthe plurality of user interface objects. The method further includes, inresponse to detecting the movement of the contact: in accordance with adetermination that output criteria have been met, generating tactileoutputs that correspond to a respective boundary of the respective userinterface object and subdivisions of the respective user interfaceobject; and in accordance with a determination that the output criteriahave not been met, generating tactile outputs that correspond to therespective boundary of the respective user interface object withoutgenerating tactile outputs that correspond to the subdivisions of therespective user interface object.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display one or more user interface objects; atouch-sensitive surface unit configured to receive user contacts; and aprocessing unit coupled to the display unit and the touch-sensitivesurface unit. The processing unit is configured to: enable display of aplurality of user interface objects on the display unit, where each ofthe plurality of user interface objects includes a plurality ofsubdivisions; and detect movement of a contact on the touch-sensitivesurface that corresponds to movement of a focus selector over arespective user interface object in the plurality of user interfaceobjects. The processing unit is further configured to, in response todetecting the movement of the contact: in accordance with adetermination that output criteria have been met, generate tactileoutputs that correspond to a respective boundary of the respective userinterface object and subdivisions of the respective user interfaceobject; and in accordance with a determination that the output criteriahave not been met, generate tactile outputs that correspond to therespective boundary of the respective user interface object withoutgenerating tactile outputs that correspond to the subdivisions of therespective user interface object.

Thus, electronic devices with displays and touch-sensitive surfaces areprovided with faster, more efficient methods and interfaces forproviding feedback when a focus selector moves over a subdivision of auser interface object, thereby increasing the effectiveness, efficiency,and user satisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for providing feedback when afocus selector moves over a subdivision of a user interface object.

There is a need for electronic devices with faster, more efficientmethods and interfaces for providing feedback when interacting with auser interface object, for example, to more efficiently differentiatefeedback corresponding to a selection event from feedback correspondingto an activation event. Such methods and interfaces may complement orreplace conventional methods for providing feedback when interactingwith a user interface object. Such methods and interfaces reduce thecognitive burden on a user and produce a more efficient human-machineinterface. For battery-operated devices, such methods and interfacesconserve power and increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface and one ormore sensors to detect intensity of contacts with the touch-sensitivesurface. The method includes: detecting a contact on the touch-sensitivesurface, where the contact corresponds to a focus selector on thedisplay. The method further includes: detecting a gesture based on inputfrom the contact. The method further includes, in response to detectingthe gesture: in accordance with a determination that the gesturecorresponds to movement of the focus selector over a respective userinterface object without activating the respective user interfaceobject, generating a first tactile output on the touch-sensitive surfacethat corresponds to movement of the focus selector over the respectiveuser interface object; and in accordance with a determination that thegesture corresponds to an increase of intensity of the contact above anactivation intensity threshold while the focus selector is over therespective user interface object, generating a second tactile output onthe touch-sensitive surface that corresponds to activation of therespective user interface object, where the second tactile output isdifferent from the first tactile output.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display one or more user interface objects; atouch-sensitive surface unit configured to receive user contacts; and aprocessing unit coupled to the display unit and the touch-sensitivesurface unit. The processing unit is configured to: enable display ofone or more user interface objects on the display unit; detect a contacton the touch-sensitive surface unit, where the contact corresponds to afocus selector on the display unit; and detect a gesture based on inputfrom the contact. The processing unit is further configured to, inresponse to detecting the gesture: in accordance with a determinationthat the gesture corresponds to movement of the focus selector over arespective user interface object without activating the respective userinterface object, generating a first tactile output on thetouch-sensitive surface that corresponds to movement of the focusselector over the respective user interface object; and in accordancewith a determination that the gesture corresponds to an increase ofintensity of the contact above an activation intensity threshold whilethe focus selector is over the respective user interface object,generating a second tactile output on the touch-sensitive surface thatcorresponds to activation of the respective user interface object, wherethe second tactile output is different from the first tactile output.

Thus, electronic devices with displays, touch-sensitive surfaces and oneor more sensors to detect intensity of contacts with the touch-sensitivesurface are provided with faster, more efficient methods and interfacesfor providing feedback when interacting with a user interface object,thereby increasing the effectiveness, efficiency, and user satisfactionwith such devices. Such methods and interfaces may complement or replaceconventional methods for providing feedback when interacting with a userinterface object.

There is a need for electronic devices with faster, more efficientmethods and interfaces for providing feedback when a focus selectormoves over a user interface object. Such methods and interfaces maycomplement or replace conventional methods for providing feedback when afocus selector moves over a user interface object. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated devices, suchmethods and interfaces conserve power and increase the time betweenbattery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display, a touch-sensitive surface. The methodincludes displaying an application window that includes a control regionand a content region distinct from the control region on the display,where the control region includes a plurality of affordances forperforming operations on content in the content region and the contentregion displays content that includes one or more affordances integratedinto the content. The method further includes detecting a contact on thetouch-sensitive surface. The method further includes detecting a gesturethat includes movement of the contact across the touch-sensitive surfacethat corresponds to movement of a focus selector on the display acrossthe application window. The method further includes, in response todetecting the gesture: in accordance with a determination that thegesture corresponds to movement of the focus selector over a firstaffordance in the control region, generating a first tactile output onthe touch-sensitive surface that corresponds to movement of the focusselector over an affordance in the control region; and in accordancewith a determination that the gesture corresponds to movement of thefocus selector over a second affordance in the content region,generating a second tactile output on the touch-sensitive surface thatcorresponds to movement of the focus selector over an affordance in thecontent region, where the second tactile output is different from thefirst tactile output.

In accordance with some embodiments, an electronic device includes adisplay unit configured display an application window; a touch-sensitivesurface unit configured to receive user contacts; and a processing unitcoupled to the display unit and the touch-sensitive surface unit. Theprocessing unit is configured to: enable display of an applicationwindow that includes a control region and a content region distinct fromthe control region on the display, where: the control region includes aplurality of affordances for performing operations on content in thecontent region; and the content region displays content that includesone or more affordances integrated into the content. The processing unitis further configured to detect a contact on the touch-sensitive surfaceunit. The processing unit is further configured to detect a gesture thatincludes movement of the contact across the touch-sensitive surface unitthat corresponds to movement of a focus selector on the display acrossthe application window. The processor unit is further configured to, inresponse to detecting the gesture: in accordance with a determinationthat the gesture corresponds to movement of the focus selector over afirst affordance in the control region, generate a first tactile outputon the touch-sensitive surface unit that corresponds to movement of thefocus selector over an affordance in the control region; and inaccordance with a determination that the gesture corresponds to movementof the focus selector over a second affordance in the content region,generate a second tactile output on the touch-sensitive surface unitthat corresponds to movement of the focus selector over an affordance inthe content region, where the second tactile output is different fromthe first tactile output.

Thus, electronic devices with displays, touch-sensitive surfaces areprovided with faster, more efficient methods and interfaces forproviding feedback when a focus selector moves over a user interfaceobject, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for providing feedback when afocus selector moves over a user interface object.

There is a need for electronic devices with faster, more efficientmethods and interfaces for adjusting a tactile output level inaccordance with an adjustment of a volume level. Such methods andinterfaces may complement or replace conventional methods for adjustinga tactile output level. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated devices, such methods and interfaces conserve powerand increase the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface. Themethod includes: detecting a first plurality of inputs on thetouch-sensitive surface; in response to detecting the first plurality ofinputs, providing tactile feedback in accordance with a tactile outputlevel of the device; and receiving a request to adjust a volume level ofthe device by a respective amount. The method further includes, inresponse to the request to adjust the volume level: adjusting the volumelevel by the respective amount from a first non-zero volume level to asecond non-zero volume level; and adjusting the tactile output level ofthe device in accordance with the respective amount.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display information; a touch-sensitivesurface unit configured to receive contacts; a tactile feedback unitconfigured to provide tactile feedback; an audio unit configured toproduce an audio signal and an audio control signal in accordance withat least a volume level; and a processing unit coupled to the displayunit, the touch-sensitive surface unit, the tactile feedback unit, andthe audio unit. The processing unit is configured to: detect a firstplurality of inputs on the touch-sensitive surface unit; in response todetecting the first plurality of inputs, provide tactile via the tactilefeedback unit feedback in accordance with a tactile output level of thedevice; and receive a request to adjust a volume level of the device bya respective amount. The processing unit is further configured to, inresponse to the request to adjust the volume level: adjust the volumelevel by the respective amount; and adjust the tactile output level ofthe device in accordance with the respective amount.

Thus, electronic devices with displays and touch-sensitive surfaces areprovided with faster, more efficient methods and interfaces foradjusting a tactile output level in accordance with an adjustment of avolume level, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace conventional methods for adjusting a tactileoutput level.

There is a need for electronic devices with more efficient methods andinterfaces for generating a tactile output for a gesture having a firstnumber of contacts (e.g., a single contact gesture) and forgoinggeneration of a tactile output for a gesture having a second number ofcontacts (e.g., a multi-contact gesture). Such methods and interfacesmay complement or replace conventional methods for tactile outputgeneration. Such methods and interfaces reduce the cognitive burden on auser and produce a more efficient human-machine interface. Forbattery-operated devices, such methods and interfaces conserve power andincrease the time between battery charges.

In accordance with some embodiments, a method is performed at anelectronic device with a display and a touch-sensitive surface, wherethe device includes one or more sensors to detect intensity of contactswith the touch-sensitive surface. The method includes: detecting, on thetouch-sensitive surface, a gesture that includes an increase ofintensity of a contact above a respective intensity threshold. Themethod further includes, in response to detecting the gesture: inaccordance with a determination that the gesture includes a first numberof contacts, generating a tactile output on the touch-sensitive surface;and in accordance with a determination that the gesture includes asecond number of contacts different from the first number, forgoinggenerating the tactile output on the touch-sensitive surface.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display a graphical user interface; atouch-sensitive surface unit configured to receive contacts; one or moresensor units configured to detect intensity of contacts with thetouch-sensitive surface unit; a tactile output unit configured togenerate a tactile output; and a processing unit coupled to the displayunit, the touch-sensitive surface unit, the one or more sensor units,and the tactile output unit. The processing unit is configured todetect, on the touch-sensitive surface unit, a gesture that includes anincrease of intensity of a contact above a respective intensitythreshold. The processing unit is further configured to, in response todetecting the gesture: in accordance with a determination that thegesture includes a first number of contacts, generate a tactile outputvia the tactile output unit on the touch-sensitive surface unit; and inaccordance with a determination that the gesture includes a secondnumber of contacts different from the first number, forgo generating thetactile output on the touch-sensitive surface unit.

Thus, electronic devices with displays, touch-sensitive surfaces, andone or more sensors to detect intensity of contacts with thetouch-sensitive surface are provided with more efficient methods andinterfaces for generating a tactile output for a gesture having a firstnumber of contacts and forgoing generation of a tactile output for agesture having a second number of contacts, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor generating a tactile output for a gesture having a first number ofcontacts and forgoing generation of a tactile output for a gesturehaving a second number of contacts.

In accordance with some embodiments, an electronic device includes adisplay, a touch-sensitive surface, optionally one or more sensors todetect intensity of contacts with the touch-sensitive surface, one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors and the one or more programs include instructionsfor performing the operations of any of the methods referred to inparagraph [0059]. In accordance with some embodiments, a graphical userinterface on an electronic device with a display, a touch-sensitivesurface, optionally one or more sensors to detect intensity of contactswith the touch-sensitive surface, a memory, and one or more processorsto execute one or more programs stored in the memory includes one ormore of the elements displayed in any of the methods referred to inparagraph [0059], which are updated in response to inputs, as describedin any of the methods referred to in paragraph [0059]. In accordancewith some embodiments, a computer readable storage medium has storedtherein instructions which when executed by an electronic device with adisplay, a touch-sensitive surface, and optionally one or more sensorsto detect intensity of contacts with the touch-sensitive surface, causethe device to perform the operations of any of the methods referred toin paragraph [0059]. In accordance with some embodiments, an electronicdevice includes: a display, a touch-sensitive surface, and optionallyone or more sensors to detect intensity of contacts with thetouch-sensitive surface; and means for performing the operations of anyof the methods referred to in paragraph [0059]. In accordance with someembodiments, an information processing apparatus, for use in anelectronic device with a display and a touch-sensitive surface,optionally one or more sensors to detect intensity of contacts with thetouch-sensitive surface, includes means for performing the operations ofany of the methods referred to in paragraph [0059].

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5M illustrate exemplary user interfaces for providing feedbackwhen a focus selector moves over a user interface object in accordancewith some embodiments.

FIGS. 6A-6C are flow diagrams illustrating a method of providingfeedback when a focus selector moves over a user interface object inaccordance with some embodiments.

FIG. 7 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 8A-8E illustrate exemplary user interfaces for providing feedbackwhen interacting with a user interface object in accordance with someembodiments.

FIGS. 8F-8H illustrate exemplary waveforms of movement profiles forgenerating tactile outputs in accordance with some embodiments.

FIG. 9 is a flow diagram illustrating a method of providing feedbackwhen interacting with a user interface object in accordance with someembodiments.

FIG. 10 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 11A-11D illustrate exemplary user interfaces for providingfeedback when a focus selector moves over a user interface object inaccordance with some embodiments.

FIGS. 11E-11G illustrate exemplary waveforms of movement profiles forgenerating tactile outputs in accordance with some embodiments.

FIGS. 12A-12B are flow diagrams illustrating a method of providingfeedback when a focus selector moves over a user interface object inaccordance with some embodiments.

FIG. 13 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 14A-14I illustrate exemplary user interfaces for adjusting atactile output level in accordance with an adjustment of a volume levelin accordance with some embodiments.

FIGS. 15A-15C are flow diagrams illustrating a method of adjusting atactile output level in accordance with an adjustment of a volume levelin accordance with some embodiments.

FIG. 16 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 17A-17F illustrate exemplary user interfaces for generating atactile output for a gesture having a first number of contacts andforgoing generation of a tactile output for a gesture having a secondnumber of contacts in accordance with some embodiments.

FIG. 18 is a flow diagram illustrating a method of generating a tactileoutput for a gesture having a first number of contacts and forgoinggeneration of a tactile output for a gesture having a second number ofcontacts in accordance with some embodiments.

FIG. 19 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The methods, devices and GUIs described herein provide visual and/orhaptic feedback that makes manipulation of user interface objects moreefficient and intuitive for a user. For example, in a system where theclicking action of a trackpad is decoupled from the contact intensity(e.g., contact force, contact pressure, or a substitute therefore) thatis needed to reach an activation threshold, the device can generatedifferent tactile outputs (e.g., “different clicks”) for differentactivation events (e.g., so that clicks that accomplish a particularresult are differentiated from clicks that do not produce any result orthat accomplish a different result from the particular result).Additionally, tactile outputs can be generated in response to otherevents that are not related to increasing intensity of a contact, suchas generating a tactile output (e.g., a “detent”) when a user interfaceobject is moved to a particular position, boundary or orientation, orwhen an event occurs at the device.

Additionally, in a system where a trackpad or touch-screen display issensitive to a range of contact intensity that includes more than one ortwo specific intensity values (e.g., more than a simple on/off, binaryintensity determination), the user interface can provide responses(e.g., visual or tactile cues) that are indicative of the intensity ofthe contact within the range. In some implementations, apre-activation-threshold response and/or a post-activation-thresholdresponse to an input are displayed as continuous animations. As oneexample of such a response, a preview of an operation is displayed inresponse to detecting an increase in contact intensity that is stillbelow an activation threshold for performing the operation. As anotherexample of such a response, an animation associated with an operationcontinues even after the activation threshold for the operation has beenreached. Both of these examples provide a user with a continuousresponse to the force or pressure of a user's contact, which provides auser with visual and/or haptic feedback that is richer and moreintuitive. More specifically, such continuous force responses give theuser the experience of being able to press lightly to preview anoperation and/or press deeply to push “past” or “through” a predefineduser interface state corresponding to the operation.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, multiple contact intensitythresholds can be monitored by the device and different functions can bemapped to different contact intensity thresholds. This serves toincrease the available “gesture space” providing easy access to advancedfeatures for users who know that increasing the intensity of a contactat or beyond a second “deep press” intensity threshold will cause thedevice to perform a different operation from an operation that would beperformed if the intensity of the contact is between a first“activation” intensity threshold and the second “deep press” intensitythreshold. An advantage of assigning additional functionality to asecond “deep press” intensity threshold while maintaining familiarfunctionality at a first “activation” intensity threshold is thatinexperienced users who are, in some circumstances, confused by theadditional functionality can use the familiar functionality by justapplying an intensity up to the first “activation” intensity threshold,whereas more experienced users can take advantage of the additionalfunctionality by applying an intensity at the second “deep press”intensity threshold.

Additionally, for a device with a touch-sensitive surface that issensitive to a range of contact intensity, the device can provideadditional functionality by allowing users to perform complex operationswith a single continuous contact. For example, when selecting a group ofobjects, a user can move a continuous contact around the touch-sensitivesurface and can press while dragging (e.g., applying an intensitygreater than a “deep press” intensity threshold) to add additionalelements to a selection. In this way, a user can intuitively interactwith a user interface where pressing harder with a contact causesobjects in the user interface to be “stickier.”

A number of different approaches to providing an intuitive userinterface on a device where a clicking action is decoupled from theforce that is needed to reach an activation threshold and/or the deviceis sensitive to a wide range of contact intensities are described below.Using one or more of these approaches (optionally in conjunction witheach other) helps to provide a user interface that intuitively providesusers with additional information and functionality, thereby reducingthe user's cognitive burden and improving the human-machine interface.Such improvements in the human-machine interface enable users to use thedevice faster and more efficiently. For battery-operated devices, theseimprovements conserve power and increase the time between batterycharges. For ease of explanation, systems, methods and user interfacesfor including illustrative examples of some of these approaches aredescribed below, as follows:

-   -   methods and user interfaces described below improve upon this        visual feedback by providing tactile feedback indicating that        the user has scrolled over or selected a particular subdivision        (e.g., individual words, letters or spaces) of the larger user        interface object (e.g., a block of text) In particular, FIGS.        5A-5M illustrate exemplary user interfaces for providing        feedback when a focus selector moves over a user interface        object. FIGS. 6A-6C are flow diagrams illustrating a method of        providing feedback when a focus selector moves over a user        interface object. The user interfaces in FIGS. 5A-5M are used to        illustrate the processes in FIGS. 6A-6C. by providing different        tactile feedback to the user when a focus selector moves over a        respective user interface object than when the user subsequently        activates the respective user interface object In particular,        FIGS. 8A-8E illustrate exemplary user interfaces for providing        feedback when interacting with a user interface object. FIG. 9        is a flow diagram illustrating a method of providing feedback        when interacting with a user interface object. The user        interfaces in FIGS. 8A-8E are used to illustrate the processes        in FIG. 9. Many electronic devices have graphical user        interfaces that display application windows having separate        regions for displaying content-independent affordances such as        control affordances. The embodiments described below provide        improved methods and user interfaces for generating feedback to        a user navigating a complex user interface environment by        providing different tactile feedback to the user when a focus        selector moves over an affordance displayed in a control region        and an affordance displayed in a content region of an        application window. In particular, FIGS. 11A-11D illustrate        exemplary user interfaces for providing feedback when a focus        selector moves over a user interface object. FIGS. 12A-12B are        flow diagrams illustrating a method of providing feedback when a        focus selector moves over a user interface object. The user        interfaces in FIGS. 11A-11D are used to illustrate the processes        in FIGS. 12A-12B.    -   Many electronic devices change output levels of sensory        properties of the device in response to the enablement of a        setting or mode of the device. However, there are sometimes a        large number of sensory properties to adjust and adjusting        output levels of these sensory properties separately can be        confusing and difficult for users. The embodiments below provide        a more convenient and intuitive user interface by adjusting a        tactile output level of a device in tandem with an adjustment of        a volume level of the device. In particular, FIGS. 14A-14I        illustrate exemplary user interfaces for adjusting a tactile        output level in accordance with an adjustment of a volume level.        FIGS. 15A-15C are flow diagrams illustrating a method of        adjusting a tactile output level in accordance with an        adjustment of a volume level. The user interfaces in FIGS.        14A-14I are used to illustrate the processes in FIGS. 15A-15C.    -   Many electronic devices provide a form of confirmation to a user        in response to an event being triggered by a user action. For        example, when a user clicks on an affordance (e.g., an icon        button) corresponding to respective content (e.g., an electronic        document, an image, or a video), an audio output is provided via        a speaker to the user to confirm that the user is clicking on        the affordance. However, this confirmation or feedback can be        distracting or confusing to a user when it occurs in response to        inputs that do not correspond to the feedback. The embodiments        described below provide a more convenient and intuitive        interface by generating a tactile output in response to        detecting a gesture that includes a first number of contacts        (e.g., one contact) and forging generating the tactile output if        the gesture includes a second number of contacts (e.g., two or        more contacts). In particular, FIGS. 17A-17F illustrate        exemplary user interfaces for generating a tactile output for a        gesture having a first number of contacts and forgoing        generation of a tactile output for a gesture having a second        number of contacts. FIG. 18 is a flow diagram illustrating a        method of generating a tactile output for a gesture having a        first number of contacts and forgoing generation of a tactile        output for a gesture having a second number of contacts. The        user interfaces in FIGS. 17A-17F are used to illustrate the        processes in FIG. 18.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU 120 and the peripherals interface118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 optionally capturesstill images or video. In some embodiments, an optical sensor is locatedon the back of device 100, opposite touch screen display 112 on thefront of the device, so that the touch screen display is enabled for useas a viewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on the touch screen display.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is coupled to input controller 160 inI/O subsystem 106. In some embodiments, the proximity sensor turns offand disables touch screen 112 when the multifunction device is placednear the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112 which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact) determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns and intensities. Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 are, optionally, used to manage an address book or contactlist (e.g., stored in application internal state 192 of contacts module137 in memory 102 or memory 370), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in a MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 are,optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 are,optionally, used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that is, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 are labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementationsfocus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

The user interface figures described below include various intensitydiagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D),and/or one or more other intensity thresholds). This intensity diagramis typically not part of the displayed user interface, but is providedto aid in the interpretation of the figures. In some embodiments, thelight press intensity threshold corresponds to an intensity at which thedevice will perform operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, the deeppress intensity threshold corresponds to an intensity at which thedevice will perform operations that are different from operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, when a contact is detected with anintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold IT₀ below which thecontact is no longer detected), the device will move a focus selector inaccordance with movement of the contact on the touch-sensitive surfacewithout performing an operation associated with the light pressintensity threshold or the deep press intensity threshold. Generally,unless otherwise stated, these intensity thresholds are consistentbetween different sets of user interface figures.

An increase of intensity of the contact from an intensity below thelight press intensity threshold IT_(L) to an intensity between the lightpress intensity threshold IT_(L) and the deep press intensity thresholdIT_(D) is sometimes referred to as a “light press” input. An increase ofintensity of the contact from an intensity below the deep pressintensity threshold IT_(D) to an intensity above the deep pressintensity threshold IT_(D) is sometimes referred to as a “deep press”input. An increase of intensity of the contact from an intensity belowthe contact-detection intensity threshold IT₀ to an intensity betweenthe contact-detection intensity threshold IT₀ and the light pressintensity threshold IT_(L) is sometimes referred to as detecting thecontact on the touch-surface. A decrease of intensity of the contactfrom an intensity above the contact-detection intensity threshold IT₀ toan intensity below the contact intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments IT₀ is greater thanzero. In some illustrations a shaded circle or oval is used to representintensity of a contact on the touch-sensitive surface. In someillustrations a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90% or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

User Interfaces and Associated Processes Conditionally Providing TactileFeedback Corresponding to Subdivisions of a User Interface Object

Many electronic devices have graphical user interfaces that display aplurality of user interface object at the same time. For example, agraphical user interface will, in some circumstances, simultaneouslydisplay any combination of multiple blocks of text, web browsers, menus,application windows, toolbars, status bars and the like, providing theuser with a large number of potential inputs and functionalities.Moreover, many of these user interface objects will have a number ofselectable or activatable user interface objects displayed therein,e.g., subdivisions of the larger user interface object. Given thecomplexity of a user interface environment that arises from displayingmultiple user interface objects having a number of functionalsubdivisions displayed therein, there is a need to provide feedback thatenables the user to more efficiently and conveniently navigate throughthe user interface environment.

The embodiments described below provide improved methods and userinterfaces for generating feedback to a user navigating a complex userinterface. More specifically, these methods and user interfaces providetactile feedback to the user when a focus selector moves over a userinterface object. The tactile feedback allows the user to moreefficiently discern between subdivisions of a user interface object,instead of or in addition to audible and/or visual feedback. Forexample, existing methods for selecting a sub-set of text within alarger block of text requires the user drag a focus selector over thetext, causing a change in the visual appearance of individual words,letters and/or spaces selected. These approaches only provide visualconfirmation that the desired sub-set of text has been selected prior tofurther manipulation (e.g., copying, editing, deleting, pasting orformatting). Advantageously, the methods and user interfaces describedbelow improve upon this visual feedback by providing tactile feedbackindicating that the user has scrolled over or selected a particularsubdivision (e.g., individual words, letters or spaces) of the largeruser interface object (e.g., a block of text).

Moreover, the methods and user interfaces described below allow thetactile feedback to be conditional upon a particular action performed bythe user. That is, the tactile outputs are, optionally, selectivelyquieted, as desired. For example, when scrolling over or selecting alarge sub-set of text, the tactile output are, optionally, conditionallysuppressed when the focus selector is moved rapidly over the text, whenthe user does not require a high level of feedback from the userinterface, and then generated again when the focus selector is movedmore slowly. In this fashion, the user is provided additional feedbackwhen trying to determine the precise endpoint of the desired text,providing increased productivity and an overall more efficient userexperience. Although exemplified by the selection of a sub-set of text,the methods and user interfaces described below are useful for improvinga user's efficiency when working with any number of user interfaceobjects and subdivisions thereof. For example, web browsers displayingmultiple hyperlinks, directory menus displaying multiple folders,application icons and/or application icons, and spreadsheets containingmultiple individual cells.

FIGS. 5A-5L illustrate exemplary user interfaces for providing feedbackwhen a focus selector moves over a user interface object in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 6A-6C.

FIGS. 5E-5I include intensity diagrams that show the current intensityof the contact on the touch-sensitive surface relative to a plurality ofintensity thresholds including a first intensity threshold (e.g., lightpress intensity threshold “IT_(L)”) and a second threshold (e.g., deeppress intensity threshold “IT_(D)”). FIGS. 5C, 5D, and 5K includevelocity diagrams that show the current velocity of the contact on thetouch-sensitive surface relative to a first velocity threshold (e.g., afast velocity threshold “VT_(F)”) and a second threshold (e.g., a slowvelocity threshold VT_(S)”). In some embodiments, the second velocitythreshold is higher than the first velocity threshold. These velocitydiagrams are typically not part of the displayed user interface, but areprovided to aid in the interpretation of the figures.

FIG. 5A illustrates exemplary user interface 8708 displaying text thatincludes multiple user interface objects (e.g., paragraphs) inaccordance with some embodiments. In FIG. 5A, user interface 8708 isdisplayed on display 450 of an electronic device that also includestouch-sensitive surface 451 and one or more sensors for detectingintensity of contacts with touch-sensitive surface 451. In someembodiments, touch-sensitive surface 451 is a touch screen display thatis optionally display 450 or a separate display. User interface 8708displays a plurality of user interface objects, including first userinterface object 8702 and second user interface object 8704, where thefirst user interface object 8702 and second user interface object 8704include a plurality of subdivisions. For example, first user interfaceobject 8702, e.g., the first paragraph displayed on display 450,includes a plurality of subdivisions (e.g., individual words), includingfirst user interface object subdivision 8702-1 (i.e., the word “Four”)and second user interface object subdivision 8702-2 (i.e., the word“score”). In FIG. 5A, user interface 8708 also displays cursor 8706,controllable by the user through contacts on touch-sensitive surface451. For example, detection of movement of a contact on touch-sensitivesurface 451 corresponds to movement of cursor 8706 on user interface8708. While paragraphs 8702 and 8704 are described above as userinterface objects with subdivisions, in some embodiments, the words (orsentences) of these paragraphs are considered to be user interfaceobjects with subdivisions (e.g., the sentences are user interfaceobjects with words as subdivisions, or the words are user interfaceobjects with letters as subdivisions).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 5A-5M andFIGS. 6A-6C will be discussed with reference to display 450 and aseparate touch-sensitive surface 451, however analogous operations are,optionally, performed on a device with a touch-sensitive display system112 in response to detecting movement of the contacts described in FIGS.5A-5M on the touch-sensitive display system 112 while displaying theuser interfaces shown in FIGS. 5A-5M on the touch-sensitive displaysystem 112; in such embodiments, the focus selector is, optionally: arespective contact, a representative point corresponding to a contact(e.g., a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112, in place of cursor 8706.

FIGS. 5A-5K illustrate that contact 8710 and gesture 8712 are detectedon touch-sensitive surface 451 (e.g., movement 8712-a of contact 8710from location 8710-a in FIG. 5A to location 8710-b in FIG. 5B; movement8712-b of contact 8710 from location 8710-b in FIG. 5B to location8710-c in FIG. 5C; movement 8712-b of contact 8710 from location 8710-bin FIG. 5B to location 8710-c in FIG. 5D; movement 8712-b of contact8710 from location 8710-b in FIG. 5B to location 8710-c in FIG. 5E;movement 8712-b of contact 8710 from location 8710-b in FIG. 5B tolocation 8710-c in FIG. 5F; movement 8712-b of contact 8710 fromlocation 8710-b in FIG. 5B to location 8710-c in FIG. 5G; and/ormovement 8712-b of contact 8710 from location 8710-b in FIG. 5B tolocation 8710-c in FIG. 5H. Contact 8710 occurs at a position ontouch-sensitive surface 451 corresponding to an area on display 450occupied by first user interface object 8702 (e.g., contact 8710corresponds to a focus selector on the display, such as cursor 8706which is at or near a location of user interface object 8702). Gesture8712 includes movement of contact 8710 on touch-sensitive surface 451that corresponds to movement of focus selector (e.g., a cursor 8706) ondisplay 450 (e.g., as illustrated in FIGS. 5A-5F).

FIG. 5B illustrates that continuation of gesture 8712 includes movementof contact 8710 on touch-sensitive surface 451 that corresponds tomovement of cursor 8706 over user interface object 8702 displayed ondisplay 450 (e.g., movement of the cursor 8706 into a respective area ofthe display that is occupied by a first paragraph of text). In responseto detecting movement of contact 8710 on touch-sensitive surface 451that corresponds to movement of cursor 8706 over user interface object8702, tactile output generators 167 generate tactile outputs 8714 thatcorrespond to boundary 8703 of user interface object 8702 (e.g., abeginning of paragraph 8702).

FIGS. 5B-5C illustrate an example where, in accordance with adetermination that output criteria have been met, tactile outputgenerators 167 generate tactile outputs 8714 that correspond to boundary8703 of the user interface object 8702, as in FIG. 5B, and subdivision8702-2 (i.e., the word “score) of user interface object 8702, as in FIG.5C. FIGS. 5B and 5D illustrate an example where, in accordance with adetermination that the output criteria have not been met, tactile outputgenerators 167 generate tactile outputs 8714 that correspond to boundary8703 of the user interface object 8702, as in FIG. 5B, withoutgenerating tactile outputs that correspond to subdivision 8702-2 of userinterface object 8702, as in FIG. 5D.

In some embodiments, as illustrated in FIGS. 5C-5D, the output criteriainclude a criterion that the focus selector has a velocity that is belowa respective velocity threshold (e.g., “VT_(F)”) when the focus selectormoves over the respective user interface object. For example, asillustrated in FIG. 5C, in response to detecting movement of cursor 8706over user interface object 8702, in accordance with a determination thatan output criterion (e.g., that cursor 8706, or alternatively contact8710, has a velocity that is below a respective velocity thresholdVT_(F)) has been met (e.g., because cursor 8706, or alternativelycontact 8710, has a velocity that is below VT_(F) in FIG. 5C), tactileoutput generators 167 generate tactile outputs 8714 that correspond toboundary 8703 (e.g., as shown in FIG. 5B) of the user interface object8702 and subdivision 8702-2 (e.g., as shown in FIG. 5C). In contrast, asillustrated in FIG. 5D, in response to detecting movement of cursor 8706over user interface object 8702, in accordance with a determination thatan output criterion (e.g., that cursor 8706, or alternatively contact8710, has a velocity that is below a respective velocity thresholdVT_(F)) has not been met (e.g., because cursor 8706, or alternativelycontact 8710, has a velocity below VT_(F) in FIG. 5D), tactile outputgenerators 167 generate tactile outputs 8714 that correspond to boundary8703 (e.g., as shown in FIG. 5B) of the user interface object withoutgenerating tactile outputs that correspond to subdivision 8702-2 (e.g.,as shown in FIG. 5D).

In some embodiments, as illustrated in FIGS. 5E-5F, the output criteriainclude a criterion that the contact has an intensity above a respectiveintensity threshold (e.g., “IT_(D)”) when the focus selector moves overthe respective user interface object. For example, as illustrated inFIG. 5E, in response to detecting movement of cursor 8706 over userinterface object 8702, in accordance with a determination that an outputcriterion (e.g., that contact 8710 has an intensity above a respectiveintensity threshold “IT_(D)”) has not been met (e.g., because contact8710 has an intensity below IT_(D) in FIG. 5E), tactile outputgenerators 167 generate tactile outputs 8714 that correspond to boundary8703 of the user interface object (e.g., as shown in FIG. 5B) withoutgenerating tactile outputs that correspond to subdivision 8702-2. Incontrast, as illustrated in FIG. 5F, in response to detecting movementof cursor 8706 over user interface object 8702, in accordance with adetermination that an output criterion (e.g., that contact 8710 has anintensity above a respective intensity threshold “IT_(D)”) has been met(e.g., because contact 8710 has an intensity above IT_(D) in FIG. 5F),tactile output generators 167 generate tactile outputs 8714 thatcorrespond to boundary 8703 of the user interface object 8702 (e.g., asshown in FIG. 5B) and subdivision 8702-2 (e.g., as shown in FIG. 5F).

In some embodiments, as illustrated in FIGS. 5G-5H, the output criteriainclude a criterion that the contact has an intensity below a respectiveintensity threshold (e.g., “IT_(D)”) when the focus selector moves overthe respective user interface object. For example, as illustrated inFIG. 5G, in response to detecting movement of cursor 8706 over userinterface object 8702, in accordance with a determination that an outputcriterion (e.g., that contact 8710 has an intensity below a respectiveintensity threshold IT_(D)) has been met (e.g., because contact 8710 hasan intensity below IT_(D) in FIG. 5G), tactile output generators 167generate tactile outputs 8714 that correspond to boundary 8703 (e.g., asshown in FIG. 5B) of the user interface object 8702 and subdivision8702-2 (e.g., as shown in FIG. 5G). In contrast, as illustrated in FIG.5H, in response to detecting movement of cursor 8706 over user interfaceobject 8702, in accordance with a determination that an output criterion(e.g., that contact 8710 has an intensity below a respective intensitythreshold IT_(D)) has not been met (e.g., because contact 8710 has anintensity above IT_(D) in FIG. 5H), tactile output generators 167generate tactile outputs 8714 that correspond to boundary 8703 (e.g., asshown in FIG. 5B) of the user interface object without generatingtactile outputs that correspond to subdivision 8702-2 (e.g., as shown inFIG. 5H).

FIGS. 5I-5K illustrates an example, where first user interface object8702 and second user interface object 8704 include a hierarchy ofsubdivisions, including a level corresponding to a first class ofsubdivisions and a level corresponding to a second class ofsubdivisions. For example, first user interface object 8702, e.g., thefirst paragraph displayed on display 450, includes a first class ofsubdivisions (e.g., individual words), including first user interfaceobject subdivision 8702-1 (i.e., the word “Four”) and second userinterface object subdivision 8702-2 (i.e., the word “score”), and asecond class of subdivisions (e.g., individual letters), including firstuser interface super-subdivision 8702-1 a (i.e., the letter “F”) andsecond user interface super-subdivision 8702-1 b (i.e., the letter “o”).

FIGS. 5I-5K illustrate tactile outputs generated in response todetecting a continuation of gesture 8712 includes movement of contact8710 on touch-sensitive surface 451 that corresponds to movement ofcursor 8706 over first user interface object 8702 and second userinterface object 8704 displayed on display 450 (e.g., movement of thecursor into a respective area of the display that is occupied by a firstparagraph of text followed by movement into a respective area of thedisplay that is occupied by a second paragraph of text). In response todetecting movement of contact 8710 on touch-sensitive surface 451 thatcorresponds to movement of cursor 8706 over user interface object 8702,tactile output generators 167 generate tactile outputs 8714 thatcorrespond to boundary 8703 of user interface object 8702, as shown inFIG. 5B.

In some embodiments, illustrated in FIGS. 5I-5K, in accordance with adetermination that first output criteria have been met, tactile outputgenerators 167 generate: tactile outputs 8722-1 a and 8724-1 a thatcorrespond to respective boundaries of first user interface object 8702and second user interface object 8704; and tactile outputs (e.g.,tactile outputs 8722-2 a and 8724-2 a) that correspond to respectiveboundaries of first class subdivisions (e.g., individual words) 8702-2to 8702-30 and 8704-2 to 8704-73, without generating tactile outputscorresponding to subdivisions in the second class of subdivisions (e.g.,individual letters), and in accordance with a determination that secondoutput criteria have been met, (optionally, in addition to adetermination that the first output criteria have been met) tactileoutput generators 167 generate tactile outputs: 8722-1 a and 8724-1 athat correspond to respective boundaries of first user interface object8702 and second user interface object 8704; tactile outputs 8722-2 a and8724-2 a that correspond to respective boundaries of first classsubdivisions (e.g., individual words) 8702-2 to 8702-30 and 8704-2 to8704-73; and tactile outputs (e.g., tactile outputs 8722-1 b and 8724-1b) that correspond to respective boundaries of second class subdivisions(e.g., individual letters) including subdivisions 8702-1 b to 8702-2 dand 8704-1 b to 8704-1 c. In some embodiments, for a user interfaceobject that is an application window with a block of text, the first andsecond subdivision levels include two or more of: paragraphs, sentences,words, and letters.

In some embodiments where tactile outputs are generated for differenttypes of boundaries (e.g., boundaries of user interface objects,boundaries of the first class of subdivisions and boundaries of thesecond class of subdivisions), the tactile outputs generated for a firsttype of boundary are different from the tactile outputs generated for asecond type of boundary. For example, in FIGS. 5I-5K, the tactileoutputs 8722-1 a and 8724-1 a that correspond to respective boundariesof first user interface object 8702 and second user interface object8704 have a first magnitude and/or movement profile; the tactile outputs8722-2 a and 8724-2 a that correspond to respective boundaries of firstclass subdivisions (e.g., individual words) 8702-2 and 8704-2 have asecond magnitude and/or movement profile that is different from thefirst magnitude/movement profile. Similarly, tactile outputs 8722-1 band 8724-1 b that correspond to respective boundaries of second classsubdivisions (e.g., individual letters) 8702-1 b and 8704-1 b have athird magnitude and/or movement profile that is different from the firstmagnitude/movement profile and the second magnitude/movement profile.While the different types of boundaries are shown in FIGS. 5I-5K asbeing associated with tactile outputs with different magnitudes and/ormovement profiles, in some embodiments, some or all of the differenttypes of boundaries are associated with tactile outputs with the same orsubstantially similar magnitudes and/or movement profiles.

FIG. 5I illustrates an example where the output criteria includecriteria based on contact intensity. In some of these embodiments, ifthe focus selector moves over a row of text while the user is pressingdown very hard with the contact (e.g., with an intensity above a secondintensity threshold “IT_(D)”), the device generates tactile outputscorresponding to the beginnings or ends of paragraphs or sentences,individual words, and individual letters. In contrast, when the focusselector moves over a row of text while the user is pressing downslightly less hard with the contact (e.g., with an intensity below asecond intensity threshold “IT_(D)” but above a first intensitythreshold “IT_(L)”), the device generates tactile outputs correspondingto the beginnings or ends of paragraphs or sentences and individualwords but not individual letters. In contrast, when the focus selectormoves over a row of text while the user is pressing down lightly withthe contact (e.g., with an intensity below a first intensity threshold“IT_(L)”), the device only generates tactile outputs corresponding tobeginnings or endings of paragraphs or sentences.

FIG. 5J illustrates an example where the output criteria includecriteria based on contact intensity. In some of these embodiments, ifthe focus selector moves over a row of text while the user is pressingdown very hard with the contact (e.g., with an intensity above a secondintensity threshold “IT_(D)”), the device only generates tactile outputscorresponding to beginnings or endings of paragraphs or sentences. Incontrast, when the focus selector moves over a row of text while theuser is pressing down slightly less hard with the contact (e.g., with anintensity below a second intensity threshold “IT_(D)” but above a firstintensity threshold “IT_(L)”), the device generates tactile outputscorresponding to the beginnings or ends of paragraphs or sentences andindividual words but not individual letters. In contrast, when the focusselector moves over a row of text while the user is pressing downlightly with the contact (e.g., with an intensity below a firstintensity threshold “IT_(L)”), the device generates tactile outputscorresponding to the beginnings or ends of paragraphs or sentences,individual words, and individual letters.

FIG. 5K illustrates an example where the output criteria includecriteria based on contact velocity, or optionally focus selectorvelocity. In some of these embodiments, when the contact, or optionallythe focus selector, is moving very fast (e.g., at a velocity above afast velocity threshold “VT_(F)”), the device only generates tactileoutputs corresponding to beginnings or endings of paragraphs orsentences. In contrast, when the contact, or optionally the focusselector, is moving slightly slower (e.g. at a velocity below a fastvelocity threshold “VT_(F)” but above a slow velocity threshold“VT_(S)”) the device generates tactile outputs corresponding to thebeginnings or ends of paragraphs or sentences and individual words. Incontrast, when the contact, or optionally the focus selector, is movingvery slowly (e.g., at a velocity below a slow velocity threshold“VT_(S)”), the device generates tactile outputs corresponding to thebeginnings or ends of paragraphs or sentences, individual words, andindividual letters.

FIG. 5L illustrates an example where movement 8728 of contact 8726 ontouch sensitive surface 451 corresponds to movement of cursor 8720 oversubdivision 8716-2 (e.g., a hyperlink) of user interface object 8716(e.g., an active web browser window), and in response to detectingmovement of cursor 8720 over user interface object subdivision 8716-2displayed in active user interface object 8716, where a determinationthat output criterion including that the respective user interfaceobject is displayed in an active window in the user interface has beenmet (e.g., because user interface object 8716 is active), tactile outputgenerators 167 generate tactile outputs 8714 that correspond to userinterface object subdivision 8716-2. In contrast, as illustrated in FIG.5M, continuation of gesture 8728 on touch sensitive surface 451corresponds to movement of cursor 8720 over subdivision 8718-2 (e.g., ahyperlink) of user interface object 8718 (e.g., an inactive web browserwindow), and in response to detecting movement of cursor 8720 over userinterface object subdivision 8718-2 displayed in inactive user interfaceobject 8718, where a determination that output criterion including thatthe respective user interface object is displayed in an active window inthe user interface has not been met (e.g., because user interface object8718 is inactive), tactile outputs that correspond to user interfaceobject subdivision 8718-2 are not generated.

In some embodiments, as illustrated in FIGS. 5L-5M, the plurality ofuser interface objects include application windows (e.g., web browsers,document windows, file menus, and other application windows) and thesubdivisions of the respective user interface object include selectableaffordances within the application windows. (e.g., hyperlinks, folders,controls, and document icons).

In some embodiments, as illustrated in FIGS. 5A-5K, the plurality ofuser interface objects include blocks of text (e.g., paragraphs,sentences, or words) and the subdivisions of the respective userinterface object include smaller portions of the text (e.g., sentences,words, or letters). In some embodiments, the plurality of user interfaceobjects include paragraphs and the subdivisions of the respective userinterface object include individual sentences. In some embodiments, theplurality of user interface objects include paragraphs and thesubdivisions of the respective user interface object include individualwords. In some embodiments, the plurality of user interface objectsinclude paragraphs and the subdivisions of the respective user interfaceobject include individual letters. In some embodiments, the plurality ofuser interface objects include sentences and the subdivisions of therespective user interface object include individual words. In someembodiments, the plurality of user interface objects include sentencesand the subdivisions of the respective user interface object includeindividual letters. In some embodiments, the plurality of user interfaceobjects include words and the subdivisions of the respective userinterface object include individual letters.

In some embodiments, as illustrated in FIGS. 5I-5K, a respective userinterface object of the plurality of user interface objects includes ahierarchy of subdivisions, including a level corresponding to a firstclass of subdivisions and a level corresponding to a second class ofsubdivisions (e.g., for a user interface object that is an applicationwindow with a block of text, the first and second subdivision levelsinclude two or more of: paragraphs, sentences, words, and letters). Insome embodiments, the plurality of user interface objects includeparagraphs, a first class of subdivisions includes individual sentences,a second class of subdivisions includes individual words, and a thirdclass of subdivisions includes individual letters. In some embodiments,the plurality of user interface objects include paragraphs, a firstclass of subdivisions includes individual sentences, a second class ofsubdivisions includes individual words. In some embodiments, theplurality of user interface objects include paragraphs, a first class ofsubdivisions includes individual sentences, a second class ofsubdivisions includes individual letters. In some embodiments, theplurality of user interface objects include paragraphs, a first class ofsubdivisions includes individual words, a second class of subdivisionsincludes individual letters. In some embodiments, the plurality of userinterface objects include sentences, a first class of subdivisionsincludes individual words, a second class of subdivisions includesindividual letters.

FIGS. 6A-6C are flow diagrams illustrating a method 8800 of providingfeedback when a focus selector moves over a subdivision of a userinterface object in accordance with some embodiments. The method 8800 isperformed at an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display and a touch-sensitivesurface. In some embodiments, the display is a touch screen display andthe touch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 8800 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 8800 provides an intuitive way to providefeedback when a focus selector moves over a user interface object. Themethod reduces the cognitive burden on a user when detecting feedbackwhen a focus selector moves over a user interface object, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to detect feedback when a focusselector moves over a user interface object faster and more efficientlyconserves power and increases the time between battery charges.

In some embodiments, the device displays (8802) a plurality of userinterface objects (e.g., first user interface object 8702 and seconduser interface object 8704 in FIGS. 5A-5K or first user interface object8716 and second user interface object 87!6 in FIGS. 5L-5M) on a display(e.g., display 450 in FIGS. 5A-5K), where each of the plurality of userinterface objects includes a plurality of subdivisions (e.g., first userinterface object subdivisions 8702-1 and 8702-2, and second userinterface object subdivisions 8704-1 and 8704-2, in FIGS. 5A-5K or firstuser interface object subdivisions 8716-1 and 8716-2, and second userinterface object subdivisions 8718-1 and 8718-2, in FIGS. 5L-5M).

In some embodiments, the plurality of user interface objects include(8804) application windows and the subdivisions of the respective userinterface object include selectable affordances within the applicationwindows (e.g., hyperlinks, folders, controls, document icons), as shownin FIGS. 5L-5M. In other embodiments, the plurality of user interfaceobjects are (8806) paragraphs and the subdivisions are words. In otherembodiments, the plurality of user interface objects are (8808)sentences and the subdivisions are words. In yet other embodiments, theplurality of user interface objects are (8810) words and thesubdivisions are letters (e.g., the device generates tactile-outputs foreach letter if a focus selector is moving slowly over a sentence, butonly at the beginning of each word if the focus selector is movingquickly).

In some embodiments, while the device displays the user interfaceobjects, the device detects (8812) movement of a contact (e.g., contact8710 in FIGS. 5A-5H or contact 8726 in FIGS. 5L-5M) on thetouch-sensitive surface (e.g., touch-sensitive surface 451) thatcorresponds to movement of a focus selector (e.g., cursor 8706 in FIGS.5A-5K or cursor 8720 in FIGS. 5L-5M) over a respective user interfaceobject (e.g., first user interface object 8702 in FIGS. 5A-5K or firstuser interface object 8716 in FIGS. 5L-5M) in the plurality of userinterface objects.

In some embodiments, in response (8814) to detecting the movement of thecontact: in accordance with a determination that output criteria havebeen met, the device generates (8816) tactile outputs (e.g., tactileoutputs 8714 in FIGS. 5B-5C) that correspond to a respective boundary(e.g., a tactile output corresponding to boundary 8703 in FIG. 5B) ofthe respective user interface object and subdivisions (e.g., tactileoutputs corresponding to subdivisions 8702-1 and 8702-2 in FIG. 5C) ofthe respective user interface object (e.g., user interface object 8702in FIGS. 5B-5C). In some embodiments, the output criteria aresubdivision-tactile-output criteria (e.g., criteria that are used todetermined whether or not to provide tactile output corresponding tosubdivisions in a respective user interface object).

In some embodiments, the output criteria include (8818) a criterion thatthe focus selector has a velocity that is below a respective velocitythreshold when the focus selector moves over the respective userinterface object. In some embodiments, if the focus selector movesquickly over a row of text, tactile outputs are generated at thebeginning of paragraphs but not for individual sentences, words, and/orletters, whereas if the focus selector moves slowly over the row oftext, tactile outputs are generated for the beginnings of paragraphs, aswell as for individual sentences, words and/or individual letters. Insome embodiments, if the focus selector moves quickly over a row oftext, tactile outputs are generated at the beginning of sentences butnot for individual words and/or letters, whereas if the focus selectormoves slowly over the row of text, tactile outputs are generated for thebeginnings of sentences, as well as for individual words and/or letters.In some embodiments, if the focus selector moves quickly over a row oftext, tactile outputs are generated at the beginning of words but notfor individual letters, whereas if the focus selector moves slowly overthe row of text, tactile outputs are generated for the beginnings ofwords and also for individual letters.

In some embodiments, the output criteria include (8820) a criterion thatthe contact has an intensity above a respective intensity threshold whenthe focus selector moves over the respective user interface object. Insome embodiments, if the focus selector moves over a row of text whilethe user is pressing down lightly with the contact, tactile outputs aregenerated at the beginning of paragraphs but not for individualsentences, words, and/or letters, whereas if the focus selector movesover the row of text while the user is pressing down hard with thecontact, tactile outputs are generated for the beginnings of paragraphs,as well as for individual sentences, words and/or individual letters. Insome embodiments, if the focus selector moves over a row of text whilethe user is pressing down lightly with the contact, tactile outputs aregenerated at the beginning of sentences but not for individual wordsand/or letters, whereas if the focus selector moves over the row of textwhile the user is pressing down hard with the contact, tactile outputsare generated for the beginnings of sentences, as well as for individualwords and/or letters. In some embodiments, if the focus selector movesover a row of text while the user is pressing down lightly with thecontact, tactile outputs are generated at the beginning of words but notfor individual letters, whereas if the focus selector moves over the rowof text while the user is pressing down hard with the contact, tactileoutputs are generated for the beginnings of words and also forindividual letters.

In some embodiments, the output criteria include (8822) a criterion thatthe contact has an intensity below a respective intensity threshold whenthe focus selector moves over the respective user interface object. Insome embodiments, if the focus selector moves over a row of text whilethe user is pressing down hard with the contact, tactile outputs aregenerated at the beginning of paragraphs but not for individualsentences, words, and/or letters, whereas if the focus selector movesover the row of text while the user is pressing down lightly with thecontact, tactile outputs are generated for the beginnings of paragraphs,as well as for individual sentences, words and/or individual letters. Insome embodiments, if the focus selector moves over a row of text whilethe user is pressing down hard with the contact, tactile outputs aregenerated at the beginning of sentences but not for individual wordsand/or letters, whereas if the focus selector moves over the row of textwhile the user is pressing down lightly with the contact, tactileoutputs are generated for the beginnings of sentences, as well as forindividual words and/or letters. In some embodiments, if the focusselector moves over a row of text while the user is pressing down hardwith the contact, tactile outputs are generated at the beginning ofwords but not for individual letters, whereas if the focus selectormoves over the row of text while the user is pressing down lightly withthe contact, tactile outputs are generated for the beginnings of wordsand also for individual letters.

In some embodiments, the output criteria include (8824) a criterion thatthe respective user interface object is displayed in an active window inthe user interface. In some embodiments the output criteria include acriterion that the respective user interface object is displayed in anactive window in the user interface. For example, if the focus selectormoves over a row of text of a background window, tactile outputs aregenerated at the beginning of words but not for individual letters or notactile outputs are generated, whereas if the focus selector moves overa row of text of the active window, tactile outputs are generated forthe beginnings of words and, in some embodiments, also for individualletters. In some embodiments, as illustrated in FIGS. 5L-5M, tactileoutputs are generated in response to detecting movement of the focusselector when the focus selector moves over elements in the activewindow but not when the focus selector moves over elements in aninactive window. For example, if there are a plurality of web browserpages that have hyperlinks open, and the focus selector moves over aplurality of hyperlinks, tactile outputs are generated for thehyperlinks in the active browser window, but tactile outputs are notgenerated for hyperlinks in the background browser window(s).

In response (8814) to detecting the movement of the contact: inaccordance with a determination that the output criteria have not beenmet, the device generates (8826) tactile outputs (e.g., tactile outputs8714 in FIG. 5B) that correspond to the respective boundary (e.g.,boundary 8703 in FIG. 5B) of the respective user interface objectwithout generating tactile outputs that correspond to the subdivisions(e.g., subdivisions 8702-1 and 8702-2 in FIG. 5D) of the respective userinterface object (e.g., user interface object 8702 in FIGS. 5B and 5D).For example in FIGS. 5B and 5D, when the contact has a velocity aboveVT_(F), the device generates a tactile output when cursor 8706 movesover a boundary of paragraph 8702 but does not generate a tactile outputwhen cursor 8706 moves over a boundary of word 8702-2. Similarly, inFIGS. 5B and 5E, when the contact has an intensity below IT_(D), thedevice generates a tactile output when cursor 8706 moves over a boundaryof paragraph 8702 but does not generate a tactile output when cursor8706 moves over a boundary of word 8702-2.

In some embodiments, a respective user interface object of the pluralityof user interface objects includes (8836) a hierarchy of subdivisions,including a level corresponding to a first class of subdivisions (e.g.,first user interface object first class subdivisions 8702-1 and 8702-2corresponding to words in paragraph 8702 and second user interfaceobject first class subdivisions 8704-1 and 8704-2 corresponding to wordsin paragraph 8704 in FIGS. 5I-5K) and a level corresponding to a secondclass of subdivisions (e.g., first user interface object second classsubdivisions 8702-1 a, 8702-1 b, 8702-1 c and 8702-1 d, corresponding toletters in words in paragraph 8702 and second user interface objectsecond class subdivisions 8704-1 a, 8704-1 b and 8704-1 c correspondingto letters in words in paragraph 8704 in FIGS. 5I-5K). For example, fora user interface object that is an application window with a block oftext, the first and second subdivision levels include two or more of:paragraphs, sentences, words, and letters.

In some embodiments, in response (8814) to detecting the movement of thecontact: in accordance with a determination that first output criteriahave been met, the device generates (8838) tactile outputs (e.g.,tactile outputs 8722-1 a, 8722-2 a, 8724-1 a and 8724-2 a in FIG. 5K)corresponding to subdivisions in the first class of subdivisions (e.g.,first class user interface object subdivisions 8702-1, 8702-2, 8704-1and 8704-2 that correspond to words in paragraphs in FIGS. 5I-5K)without generating tactile outputs corresponding to subdivisions in thesecond class of subdivisions (e.g., second class user interface objectsubdivisions 8702-1 b, 8702-2 b, and 8704-1 b that correspond to lettersin words in FIGS. 5I-5K).

In some embodiments, in response (8814) to detecting the movement of thecontact: in accordance with a determination that second output criteriahave been met (optionally, in addition to a determination that the firstoutput criteria have been met), the device generates (8840) tactileoutputs (e.g., tactile outputs 8722-1 a, 8722-2 a, 8724-1 a and 8724-2 ain FIGS. 5I-5K) corresponding to subdivisions in the first class ofsubdivisions (e.g., first class user interface object subdivisions8702-1, 8702-2, 8704-1 and 8704-2 that correspond to words in paragraphsin FIGS. 5I-5K) and the device generates tactile outputs (e.g., tactileoutputs 8722-1 b, 8722-2 b, 8724-1 b and 8724-2 b in FIGS. 5I-5K)corresponding to subdivisions in the second class of subdivisions (e.g.,second class user interface object subdivisions 8702-1 b, 8702-2 b, and8704-1 b that correspond to letters in words in FIGS. 5I-5K). Forexample, when the contact is moving very fast, the device only generatestactile outputs corresponding to ends of sentences, when the contact ismoving slightly slower the device generates tactile outputscorresponding to the ends of words and sentences, and when the contactis moving very slowly, the device generates tactile outputscorresponding to the ends of words, sentences, and individual letters.

It should be understood that the particular order in which theoperations in FIGS. 6A-6C have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in paragraph [0059]) are also applicable in an analogousmanner to method 8800 described above with respect to FIGS. 6A-6C. Forexample, the contacts, gestures, user interface objects, tactileoutputs, intensity thresholds, velocity thresholds and focus selectorsdescribed above with reference to method 8800 optionally have one ormore of the characteristics of the contacts, gestures, user interfaceobjects, tactile outputs, intensity thresholds, velocity thresholds andfocus selectors described herein with reference to other methodsdescribed herein (e.g., those listed in paragraph [0059]). For brevity,these details are not repeated here.

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of an electronic device 8900 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 7 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 7, an electronic device 8900 includes a display unit8902 configured to display one or more user interface objects, atouch-sensitive surface unit 8904 configured to receive user contacts,optionally one or more sensor units 8906 configured to detect intensityof contacts with the touch-sensitive surface unit 8904; and a processingunit 8908 coupled to the display unit 8902, the touch-sensitive surfaceunit 8904 and the one or more sensor units 8906. In some embodiments,the processing unit 8908 includes a display enabling unit 8909, adetecting unit 8910, and a generating unit 8912.

In some embodiments, the processing unit 8908 is configured to enabledisplay (e.g., with the display enabling unit 8909) of a plurality ofuser interface objects on the display unit 8902, where each of theplurality of user interface objects includes a plurality ofsubdivisions. In some embodiments, the processing unit 8908 is furtherconfigured to detect movement of a contact on the touch-sensitivesurface that corresponds to movement of a focus selector over arespective user interface object in the plurality of user interfaceobjects (e.g., with the detecting unit 8910); and in response todetecting the movement of the contact: in accordance with adetermination that output criteria have been met, the processing unit8908 is configured to generate tactile outputs (e.g., with thegenerating unit 8912) that correspond to a respective boundary of therespective user interface object and subdivisions of the respective userinterface object; and in accordance with a determination that the outputcriteria have not been met, the processing unit 8908 is configured togenerate tactile outputs (e.g., with the generating unit 8912) thatcorrespond to the respective boundary of the respective user interfaceobject without generating tactile outputs that correspond to thesubdivisions of the respective user interface object.

In some embodiments, the output criteria include a criterion that thefocus selector has a velocity that is below a respective velocitythreshold when the focus selector moves over the respective userinterface object.

In some embodiments, the output criteria include a criterion that thecontact has an intensity above a respective intensity threshold when thefocus selector moves over the respective user interface object.

In some embodiments, the output criteria include a criterion that thecontact has an intensity below a respective intensity threshold when thefocus selector moves over the respective user interface object.

In some embodiments, the output criteria include a criterion that therespective user interface object is displayed in an active window in theuser interface.

In some embodiments, the plurality of user interface objects includeapplication windows and the subdivisions of the respective userinterface object include selectable affordances within the applicationwindows.

In some embodiments, the plurality of user interface objects areparagraphs, and the subdivisions are words.

In some embodiments, the plurality of user interface objects aresentences, and the subdivisions are words.

In some embodiments, the plurality of user interface objects are words,and the subdivisions are letters.

In some embodiments, a respective user interface object of the pluralityof user interface objects includes a hierarchy of subdivisions,including a level corresponding to a first class of subdivisions and alevel corresponding to a second class of subdivisions. In some of theseembodiments, in response to detecting the movement of the contact: inaccordance with a determination that first output criteria have beenmet, the processing unit 8908 is configured to generate tactile outputs(e.g., with the generating unit 8912) corresponding to subdivisions inthe first class of subdivisions without generating tactile outputscorresponding to subdivisions in the second class of subdivisions; andin accordance with a determination that second output criteria have beenmet, the processing unit 8908 is configured to generate tactile outputs(e.g., with the generating unit 8912) corresponding to subdivisions inthe first class of subdivisions and generate tactile outputs (e.g., withthe generating unit 8912) corresponding to subdivisions in the secondclass of subdivisions.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 6A-6C are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 7.For example, detection operation 8812 and determination operations 8816,8826, 8838 and 8840 are, optionally, implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface or generation of atactile output (e.g., corresponding to a boundary of a user interfaceobject or subdivision thereof). When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally utilizes or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

Providing Tactile Feedback when Interacting with a User Interface Object

Many electronic devices have graphical user interfaces that display userinterface objects that can be activated in response to a user input(e.g., by clicking or scrolling over the object). For example, agraphical user interface optionally displays an application windowcontaining a button, hyperlink, document launch icon, application launchicon, menu or other selectable affordance associated with a particularaction (e.g., launching an application, loading content associated witha hyperlink or manipulating an object within an application). Typically,a user accesses the activatable content by first selecting theappropriate user interface object (e.g., via moving a focus selectorover the object) and secondly activating the user interface object(e.g., via “clicking” on the object). Given the complexity of a userinterface environment containing multiple user interface objectsassociated with activatable content, there is a need to provide feedbackthat enables the user to more efficiently and conveniently navigatethrough the user interface environment.

The embodiments described below provide improved methods and userinterfaces for providing feedback to a user navigating a complex userinterface environment. More specifically, these methods and userinterfaces provide different tactile feedback to the user when a focusselector moves over a respective user interface object than when theuser subsequently activates the respective user interface object. Thetactile feedback distinguishes between these two actions by providingphysical cues that feel different to the user. In this fashion, themethods and user interfaces provided below allow the user to moreefficiently and conveniently discern between these two actions byproviding tactile feedback, instead of or in addition to audible and/orvisual feedback. Some methods for distinguishing between the selectionand activation of a user interface object rely on an audible or visualcue. However, there are many situations (e.g., at work, in a theatre andin various social situations) where the volume of an electronic devicewill be lowered or muted, rendering audible cues ineffective.Advantageously, the methods and user interfaces described below augmentor replace audible feedback by providing tactile feedback indicatingthat a user interface object has been selected and/or activated.

FIGS. 8A-8E illustrate exemplary user interfaces for providing feedbackwhen interacting with a user interface object in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIG. 9. FIGS.8A-8D include intensity diagrams that show the current intensity of thecontact on the touch-sensitive surface relative to a plurality ofintensity thresholds including an activation intensity threshold (e.g.,light press intensity threshold “IT_(L)”). In some embodiments,operations similar to those described below with reference to IT_(L) areperformed with reference to a different intensity threshold (e.g.,“IT_(D)”). These intensity diagrams are typically not part of thedisplayed user interface, but are provided to aid in the interpretationof the figures. FIGS. 8B-8D include waveform diagrams that show theamplitude (e.g., a high amplitude “AH” or low amplitude “AL”) and shape(e.g., square or sawtooth) of the waveform corresponding to tactileoutput generated on the touch-sensitive surface in response to a tactileoutput triggering event (e.g., selection or activation of a userinterface object). These waveform diagrams are typically not part of thedisplayed user interface, but are provided to aid in the interpretationof the figures.

FIG. 8A illustrates exemplary user interface 9008 displaying one or moreuser interface objects 9004. For example, user interface 9008 displaysweb browser 9002 (e.g., a user interface application window) thatincludes navigation button 9004-1 (e.g., a user interface object with anactivatable hyperlink) and cursor 9006 (e.g., a focus selector). In FIG.8A, user interface 9008 is displayed on display 450 of an electronicdevice that also includes touch-sensitive surface 451 and one or moresensors for detecting intensity of contacts with touch-sensitivesurface. In some embodiments, touch-sensitive surface 451 is a touchscreen display that is optionally display 450 or a separate display.

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 8A-8H andFIG. 9 will be discussed with reference to display 450 and a separatetouch-sensitive surface 451, however analogous operations are,optionally, performed on a device with a touch-sensitive display system112 in response to detecting movement of the contacts described in FIGS.8A-8H on the touch-sensitive display system 112 while displaying theuser interfaces shown in FIGS. 8A-8H on the touch-sensitive displaysystem 112; in such embodiments, the focus selector is, optionally: arespective contact, a representative point corresponding to a contact(e.g., a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112, in place of cursor 9006.

FIGS. 8A-8E illustrate various embodiments where cursor 9006, controlledby contact 9010 on touch-sensitive surface 451 and movement 9012thereof, moves over (e.g., selects) and then clicks (e.g., activates)user navigation button 9006. In response, tactile output generators 167provide different feedback (e.g., tactile outputs 9014, 9018 and 9022)to the user, identifying the actions as either selection or activationevents. For example, depending on the type of action (e.g., selection oractivation), the tactile outputs have a unique waveform (e.g., squarewaveforms 9016 and 9024 or sawtooth waveform 9020) or amplitude (e.g., ahigh amplitude “AH” or low amplitude “AL”) indicating to the user whichaction was performed through their sense of touch.

FIGS. 8A-8E illustrate that contact 9010, corresponding to cursor 9002displayed on display 450, and a gesture including movement 9012 ofcontact 9010 (e.g., movement 9012-a of contact 9010 from location 9010-ain FIG. 8A to location 9010-b in FIG. 8B) or change in intensity ofcontact 9010 (e.g., change in intensity of contact 9010 from anintensity below IT_(L) in FIGS. 8A-8B to an intensity above IT_(L) inFIG. 8C-8D; and/or liftoff of contact 9010 in FIG. 8C or FIG. 8D, asillustrated in FIG. 8E) are detected on touch-sensitive surface 451.Contact 9010 is detected at a position on touch-sensitive surface 451corresponding to an area on display 450 occupied by focus selector 9006(e.g., contact 9010 corresponds to a focus selector on the display, suchas cursor 9006 which is at or near a location of user interface object9002). In some embodiments, movement of contact 9010 on touch-sensitivesurface 451 corresponds to movement of focus selector (e.g., a cursor9006) on display 450 (e.g., as illustrated in FIGS. 8A-8B).

FIGS. 8A-8B illustrate an example of a beginning of a gesture wherecursor 9006 moves over navigation button 9004-1, in accordance withmovement 9012 of contact 9010, corresponding to cursor 9006 on display450, on touch-sensitive surface 451, without activating navigationbutton 9004-1. In FIG. 8B, the device (e.g., via tactile outputgenerators 167) generates first tactile outputs 9014 having a signaturecorresponding to a scroll over event (e.g., waveform 9016 and/or highamplitude “AH”), because the focus selector scrolled over the userinterface object without activating the user interface object.

FIGS. 8B-8D illustrate various examples where the device detects acontinuation of a gesture including movement 9012 of contact 9010, or asecond gesture initiated after the completion of movement 9012, thatincludes an increase of intensity of contact 9010 above an activationintensity threshold (e.g., light press intensity threshold “IT_(L)”). InFIGS. 8C-8D, the device (e.g., via tactile output generators 167)generates second tactile outputs 9018 or 9022 having a signaturecorresponding to an activation event (e.g., waveform 9020 and/or lowamplitude “AL”). For example, after moving a cursor over an activatableuser interface object (e.g., a hyperlink or navigation button associatedtherewith), causing the device to generate a first tactile feedback(e.g., tactile output 9014, as shown in FIG. 8B), the user pushes downwith greater force on the touch-sensitive surface to activate the userinterface object, and in response the device generates a second tactilefeedback (e.g., tactile output 9018 in FIG. 8C or tactile output 9022 inFIG. 8D) that feels different from the first tactile feedback (e.g.,tactile output 9014 in FIG. 8B).

FIGS. 8B and 8C illustrate an example where the second tactile output(e.g., tactile output 9018) has a different movement profile (e.g.,waveform 9020), but substantially the same maximum amplitude (e.g.,“AH”), as the first tactile output (e.g., tactile output 9014). Forexample, the tactile feedback corresponding to activation of the userinterface object feels different from, but is equally (or approximately)as strong as, the tactile feedback corresponding to selection of theuser interface object. In contrast, FIGS. 8B and 8D illustrate anexample where the second tactile output (e.g., tactile output 9022) hassubstantially the same movement profile (e.g., waveform 9024), but adifferent maximum amplitude (e.g. “AL”), as the first tactile output(e.g., tactile output 9014). For example, the tactile feedbackcorresponding to activation of the user interface object feels similarto, but is noticeably stronger or weaker than, the tactile feedbackcorresponding to selection of the user interface object.

FIGS. 8C-8E illustrate various examples where, in response to anincrease of intensity of contact 9010 above an activation intensitythreshold (e.g., light press intensity threshold “IT_(L)”), wherecontact 9010 corresponds to an area on display 450 occupied by focusselector 9006 located over user interface object 9004-1, the userinterface object is activated. For example, as illustrated in FIG. 8E,after the user pushes down harder on touch-sensitive surface 451 (e.g.,via contact 9010), with cursor 9006 positioned over navigation button9004-1, and lifts off the contact from the touch-sensitive surface (or,alternatively, reduces the intensity of contact 9010 to an intensitybetween IT₀ and IT_(L) without lifting contact 9010 off of thetouch-sensitive surface 451), content associated with a hyperlinkembedded within the navigation button is loaded onto web browser 9004-1(e.g., a new webpage is loaded on web browser 9002).

As described above, tactile outputs are, optionally, generated for aselection of a user interface object and an activation of a userinterface object. FIGS. 8F-8H illustrate example waveforms of movementprofiles for generating these tactile outputs. FIG. 8F illustrates asawtooth waveform. FIG. 8G illustrates a square waveform and FIG. 8Hillustrates a square waveform that has a lower amplitude than the squarewaveform of FIG. 8G. The high-amplitude square movement profile in FIG.8G is, optionally, associated with moving over (e.g., scrolling over) auser interface object; the tactile output generated for moving over(e.g., scrolling over) a user interface object is, optionally, generatedin accordance with a high-amplitude square movement profile. Thelow-amplitude square movement profile in FIG. 8H is, optionally,associated with activation of a user interface object; the tactileoutput generated for activation of a user interface object are,optionally, generated in accordance with a low-amplitude square movementprofile. The sawtooth movement profile in FIG. 8F is, optionally,associated with activation of a user interface object; the tactileoutput generated for activation of a user interface object is,optionally, generated in accordance with the sawtooth movement profile.

FIG. 9 is a flow diagram illustrating a method 9100 of providingfeedback when interacting with a user interface object in accordancewith some embodiments. The method 9100 is performed at an electronicdevice (e.g., device 300, FIG. 3, or portable multifunction device 100,FIG. 1A) with a display and a touch-sensitive surface. In someembodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 9100 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 9100 provides an intuitive way to providefeedback when interacting with a user interface object. The methodreduces the cognitive burden on a user when detecting feedback wheninteracting with a user interface object, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to detect feedback when interacting with a userinterface object faster and more efficiently conserves power andincreases the time between battery charges.

In some embodiments, the device displays (9102) one or more interfaceobjects (e.g., user interface objects 9004 including one or more of theaffordances, controls, buttons or hyperlinks displayed in applicationwindow 9002) on a display (e.g., display 450 in FIGS. 8A-8E.

In some embodiments, while the device displays the user interfaceobjects, the device detects (9104) a contact (e.g., contact 9010) on atouch-sensitive surface (e.g., touch sensitive surface 451), where thecontact corresponds to a focus selector (e.g., cursor 9006) on a display(e.g., display 450). In some embodiments, the contact is a fingercontact. In some embodiments, the contact is the focus selector (e.g.,when the device has a touch screen, the focus selector is, optionally,contact 9010). In some embodiments, the contact corresponds to a cursoror selection box that is displayed on the display.

In some embodiments, while the device displays the user interfaceobjects, the device detects (9106) a gesture based on input from thecontact (e.g., movement 9012 of contact 9010 in FIGS. 8A-8B, increase ofintensity of contact 9010 in FIGS. 8B-8D, and/or liftoff of contact 9010in FIGS. 8C-8E). In some embodiments, the gesture includes a change inintensity of the contact. In some embodiments, the gesture includesmovement of the contact. In some embodiments, the gesture includes bothmovement of the contact and a change in intensity of the contact.

In some embodiments, in response (9108) to detecting the gesture: inaccordance with a determination that the gesture corresponds to movementof the focus selector over a respective user interface object (e.g.,navigation button 9004-1) without activating the respective userinterface object (e.g., moving a mouse cursor over a button withoutactivating the button), the device generates (9110) a first tactileoutput (e.g., tactile output 9014 in FIG. 8B) on the touch-sensitivesurface that corresponds to movement of the focus selector over therespective user interface object (e.g., navigation button 9004-1). Insome embodiments, the respective user interface object is a button, ahyperlink, a document icon, an application launch icon or anotherselectable affordance.

In response (9108) to detecting the gesture: in accordance with adetermination that the gesture corresponds to an increase of intensityof the contact above an activation intensity threshold (e.g., lightpress intensity threshold “IT_(L)”) while the focus selector is over therespective user interface object, the device generates (9112) a secondtactile output (e.g., tactile output 9018 in FIG. 8C or 9022 in FIG. 8D)on the touch-sensitive surface that corresponds to activation of therespective user interface object, where the second tactile output isdifferent from the first tactile output. For example, where a “detent”(e.g., tactile output 9014 in FIG. 8B) that is generated on thetouch-sensitive surface when a user moves a cursor/contact over a userinterface object feels different from a “click” (e.g., tactile output9018 in FIG. 8C or tactile output 9022 in FIG. 8D) that is generated onthe touch-sensitive surface when a user activates the user interfaceobject. In some embodiments, the first tactile output is more prominent(e.g., has a larger amplitude) than the second tactile output. In someembodiments, the second tactile output is more prominent (e.g., has alarger amplitude) than the first tactile output.

In some embodiments, in response (9108) to detecting the gesture: inaccordance with a determination that the gesture corresponds to anincrease of intensity of the contact above an activation intensitythreshold (e.g., light press intensity threshold “IT_(L)”) while thefocus selector is over the respective user interface object, the deviceactivates (9114) the respective user interface object (e.g., loadscontent associated with a hyperlink embedded with navigation button9004-1, as illustrated in FIG. 8E). In some embodiments, activating theuser interface object includes launching an application corresponding toan application icon or loading content associated with a hyperlink. Insome embodiments, the respective user interface object is activated inresponse to detecting an increase in intensity of the contact above theactivation intensity threshold (e.g., the down stroke of the pressinput). In some embodiments, the respective user interface object isactivated in response to detecting an increase in intensity of thecontact above the activation intensity threshold (e.g., “IT_(L)”)followed by a subsequent decrease in intensity of the contact below theactivation intensity threshold (e.g., “IT_(L)”) or a slightly lowerhysteresis intensity threshold (e.g., the up stroke of the press input).In some embodiments, the respective user interface object is activatedin response to detecting an increase in intensity of the contact abovethe activation intensity threshold (e.g., “IT_(L)”) followed by aliftoff of the contact from the touch-sensitive surface.

In some embodiments, the first tactile output is generated (9116) bymovement of the touch-sensitive surface that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface that includes a second dominant movementcomponent, and the first dominant movement component and the seconddominant movement component have substantially a same amplitude (e.g.,high amplitude “AH” in FIGS. 8B-8C) and substantially different movementprofiles (e.g., square waveform 9016 in FIGS. 8B and 8G and sawtoothwaveform 9020 in FIGS. 8C and 8F). In some embodiments, movement of thetouch-sensitive surface corresponds to an initial impulse, ignoring anyunintended resonance. In some embodiments, the movement profiles differin their waveform shape (e.g., square, sine, squine, triangle orsawtooth waveform shape), waveform pulse width and/or waveform pulseperiod (e.g., frequency). For example, as illustrated in FIGS. 8B-8C, a“detent” that is generated on the touch-sensitive surface when a usermoves a cursor/contact over a user interface object has a squarewaveform movement profile (e.g., waveform 9016 in FIGS. 8B and 8G),whereas a “click” that is generated on the touch-sensitive surface whena user activates the user interface object has a sawtooth waveformmovement profile (e.g., waveform 9020 in FIGS. 8C and 8F), or viceversa.

In some embodiments, the first tactile output is generated (9118) bymovement of the touch-sensitive surface that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface that includes a second dominant movementcomponent, and the first dominant movement component and the seconddominant movement component have a substantially same movement profile(e.g., square waveform 9016 in FIGS. 8B and 8G and square waveform and9024 in FIGS. 8D and 8H) and substantially different amplitudes (e.g.,high amplitude “AH” in FIG. 8B and low amplitude “AL” in FIG. 8D). Insome embodiments, movement of the touch-sensitive surface corresponds toan initial impulse, ignoring any unintended resonance. For example, asillustrated in FIGS. 8B and 8D, a “detent” that is generated on thetouch-sensitive surface when a user moves a cursor/contact over a userinterface object has greater amplitude than a “click” that is generatedon the touch-sensitive surface when a user activates the user interfaceobject (e.g., high amplitude “AH” of tactile output 9014 in FIG. 8B isgreater than low amplitude “AL” of tactile output 9022 in FIG. 8D), orvice versa.

It should be understood that the particular order in which theoperations in FIG. 9 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in paragraph [0059]) are also applicable in an analogousmanner to method 9100 described above with respect to FIG. 9. Forexample, the contacts, gestures, user interface objects, tactilesensations, intensity thresholds and focus selectors described abovewith reference to method 9100 optionally have one or more of thecharacteristics of the contacts, gestures, user interface objects,tactile sensations, intensity thresholds and focus selectors describedherein with reference to other methods described herein (e.g., thoselisted in paragraph [0059]). For brevity, these details are not repeatedhere.

In accordance with some embodiments, FIG. 10 shows a functional blockdiagram of an electronic device 9200 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 10 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 10, an electronic device 9200 includes a display unit9202 configured to display one or more user interface objects, atouch-sensitive surface unit 9204 configured to receive user contacts,one or more sensor units 9206 configured to detect intensity of contactswith the touch-sensitive surface unit 9204; and a processing unit 9208coupled to the display unit 9202, the touch-sensitive surface unit 9204and the one or more sensor units 9206. In some embodiments, theprocessing unit 9208 includes a display enabling unit 9210, a detectingunit 9212, a generating unit 9214 and an activating unit 9216.

In some embodiments, the processing unit 9208 is configured to enabledisplay (e.g., with the display enabling unit 9210) of one or more userinterface objects on display unit 9202. In some embodiments, theprocessing unit 9208 is configured to detect a contact on thetouch-sensitive surface unit 9204 (e.g., with detecting unit 9212),where the contact corresponds to a focus selector on display unit 9202.In some embodiments, the processing unit 9208 is further configured todetect a gesture based on input from the contact (e.g., with detectingunit 9212); and in response to detecting the gesture: in accordance witha determination that the gesture corresponds to movement of the focusselector over a respective user interface object of the one or more userinterface objects without activating the respective user interfaceobject, the processing unit 9208 is configured to generate a firsttactile output on the touch-sensitive surface unit 9204 that correspondsto movement of the focus selector over the respective user interfaceobject (e.g., with the generating unit 9214); and in accordance with adetermination that the gesture corresponds to an increase of intensityof the contact above an activation intensity threshold while the focusselector is over the respective user interface object, the processingunit 9208 is configured to generate a second tactile output on thetouch-sensitive surface unit 9204 that corresponds to activation of therespective user interface object, where the second tactile output isdifferent from the first tactile output (e.g., with the generating unit9214).

In some embodiments, the processing unit 9208 is further configured to,in accordance with a determination that the gesture corresponds to anincrease of intensity of the contact above an activation intensitythreshold (e.g., IT_(L)) while the focus selector is over the respectiveuser interface object, activate the respective user interface object(e.g., with the activating unit 9216).

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface unit 9204 that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface unit 9204 that includes a second dominantmovement component, and the first dominant movement component and thesecond dominant movement component have a same amplitude and differentmovement profiles.

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface unit 9204 that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface unit 9204 that includes a second dominantmovement component, and the first dominant movement component and thesecond dominant movement component have a same movement profile anddifferent amplitudes.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIG. 9 are, optionally,implemented by components depicted in FIGS. 1A-1B or FIG. 10. Forexample, detection operations 9104 and 9106, determination operations9110, 9112 and 9114 and generation operations 9110 and 9112 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190, respectively. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub-event, such as selection oractivation of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application. In someembodiments, event handler 190 accesses a respective tactile outputgenerator 167 to generate a tactile output. Similarly, it would be clearto a person having ordinary skill in the art how other processes can beimplemented based on the components depicted in FIGS. 1A-1B.

Providing Tactile Feedback that Distinguishes Between User InterfaceObjects

Many electronic devices have graphical user interfaces that displayapplication windows having separate regions for displayingcontent-independent affordances (e.g., affordances which are alwaysdisplayed in the application window irrespective of the contentdisplayed), e.g., “control regions,” and content-dependent affordances(e.g., affordances which are displayed in the application window onlywhen a specific content is displayed), e.g., “content regions.” Forexample, a web browser window optionally includes a control regiondisplaying affordances that perform an operation on content displayed ina content region (e.g., moving forward and backwards in the browserhistory, inputting a URL address or bookmarking a web page) withoutbeing dependent upon the content itself. Likewise, a web browser windowoptionally includes a content region displaying affordances that areintegrated into the displayed content (e.g., a hyperlink, text box ordrop-down menu) that are associated with the particular content beingdisplayed (e.g., a web page). Given the complexity of a user interfaceenvironment where certain affordances displayed in an application windoware content-independent and other affordances are content-dependent,there is a need to provide feedback that enables the user to moreefficiently and conveniently navigate through the user interfaceenvironment.

The embodiments described below provide improved methods and userinterfaces for generating feedback to a user navigating a complex userinterface environment. More specifically, these methods and userinterfaces provide different tactile feedback to the user when a focusselector moves over an affordance displayed in a control region and anaffordance displayed in a content region of an application window. Thetactile feedback distinguishes between these two actions by providingphysical cues that feel different to the user. In this fashion, themethods and user interfaces provided below allow the user to moreefficiently and conveniently discern the type of affordance selected byproviding tactile feedback, instead of or in addition to audible and/orvisual feedback. Some methods for distinguishing between the selectionand activation of a user interface object rely on an audible or visualcue. However, there are many situations (e.g., at work, in a theatre andin various social situations) where the volume of an electronic devicewill be lowered or muted, rendering audible cues ineffective.Advantageously, the methods and user interfaces described below augmentor replace audible feedback by providing tactile feedback indicating thetype or location of an affordance displayed in an application window.

FIGS. 11A-11D illustrate exemplary user interfaces for providingfeedback when a focus selector moves over a user interface object inaccordance with some embodiments. The user interfaces in these figuresare used to illustrate the processes described below, including theprocesses in FIGS. 12A-12B. FIGS. 11A-11D include intensity diagramsthat show the current intensity of the contact on the touch-sensitivesurface relative to a plurality of intensity thresholds including acontact detection intensity threshold (e.g., “IT₀”) and a light pressintensity threshold (e.g., “IT_(L)”). In some embodiments, operationssimilar to those described below with reference to IT_(L) are performedwith reference to a different intensity threshold (e.g., “IT_(D)”). Insome embodiments, the operations described below are not dependent on anintensity of the contact. FIGS. 11B-11D include waveform diagrams thatshow the amplitude (e.g., a high amplitude “AH” or low amplitude “AL”)and shape (e.g., square or triangle) of the waveform corresponding totactile output generated on the touch-sensitive surface in response to aqualifying event (e.g., selection or activation of a user interfaceobject). These waveform diagrams are typically not part of the displayeduser interface, but are provided to aid in the interpretation of thefigures.

FIG. 11A illustrates exemplary user interface 9316 displayingapplication window 9302 that includes control region 9304 (e.g., locatedabove bar 9308) and content region 9306 (e.g., located below bar 9308)distinct from the control region. In FIG. 11A, user interface 9316 isdisplayed on display 450 of an electronic device that also includestouch-sensitive surface 451 and one or more sensors for detectingintensity of contacts with touch-sensitive surface. In some embodiments,touch-sensitive surface 451 is a touch screen display that is optionallydisplay 450 or a separate display. User interface 9316 displays controlregion 9304 that includes a plurality of affordances 9312 for performingoperations on content in the content region (e.g., icon 9312-a forsaving browser based content, icon 9312-b for navigating backwards inthe browser's history and navigation bar 9312-c for inputting a webaddress). In some embodiments, control region 9304 includes one or morecontent-dependent affordances. User interface 9316 displays contentregion 9306 displaying content that includes one or morecontent-dependent affordances 9314 (e.g., a navigation button 9314-1associated with a hyperlink) integrated into the content. User interface9316 also displays cursor 9310, controllable by the user throughcontacts on touch-sensitive surface 451. For example, detection ofmovement of a contact (e.g., a gesture) on touch-sensitive surface 451corresponds to movement of cursor 9310 on user interface 9316.

In some embodiments, the plurality of affordances in control region 9304(e.g., affordances 9312 in FIGS. 11A-11D) includes multiplecontent-independent controls that are displayed in the control region ofthe application without regard to the content that is displayed incontent region 9306.

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 11A-11Gand FIGS. 12A-12B will be discussed with reference to display 450 and aseparate touch-sensitive surface 451, however analogous operations are,optionally, performed on a device with a touch-sensitive display system112 in response to detecting movement of the contacts described in FIGS.11A-11G on the touch-sensitive display system 112 while displaying theuser interfaces shown in FIGS. 11A-11G on the touch-sensitive displaysystem 112; in such embodiments, the focus selector is, optionally: arespective contact, a representative point corresponding to a contact(e.g., a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112, in place of cursor 9310.

FIGS. 11A-11D illustrate various embodiments where cursor 9310,controlled by contact 9318 on touch-sensitive surface 451 and movement9320 thereof, moves over an affordance in either control region 9304(e.g., affordances 9312) or content region 9306 (e.g., navigation button9314-1). In response, tactile output generators 167 provide differentfeedback (e.g., tactile outputs 9322, 9326 and 9330) to the user,identifying the affordances as located in either the control region orthe content region. For example, depending on the location of theaffordance (e.g., in control region 9304 or content region 9306), thetactile outputs have a different waveform (e.g., square waveforms 9324and 9332 or sawtooth waveform 9328) and/or amplitude (e.g., a highamplitude “AH” or low amplitude “AL”) indicating to the user where theaffordance is located, so that the user can tell based on the tactileoutput whether an affordance under or near the focus selector is acontrol affordance or a content affordance.

FIGS. 11A-11D illustrate that contact 9318, corresponding to cursor 9310displayed on display 450, and a gesture including movement 9320 ofcontact 9318 (e.g., movement 9320-a of contact 9318 from location 9318-ain FIG. 11A to location 9318-b in FIG. 11B or movement 9320-b of contact9318 from location 9318-b in FIG. 11B to location 9318-c in FIG. 11C orFIG. 11D) are detected on touch-sensitive surface 451. Contact 9318 isdetected at a position on touch-sensitive surface 451 corresponding toan area on display 450 occupied by focus selector 9310 (e.g., contact9318 corresponds to a focus selector on the display, such as cursor 9310which is at or near a location of web browser window 9302). In someembodiments, movement of contact 9318 on touch-sensitive surface 451corresponds to movement of focus selector (e.g., a cursor 9310) ondisplay 450 (e.g., as illustrated in FIGS. 11A-11D).

FIGS. 11A-11B illustrate an example of a beginning of a gesture wherecursor 9310 moves over affordance 9312-a located in control region 9304of web browser window 9302, in accordance with movement 9320-a ofcontact 9318 on touch-sensitive surface 451. In FIG. 11B, the device(e.g., via tactile output generators 167) generates first tactile output9322 having a signature corresponding to an affordance (e.g., icon9312-a) located in control region 9304 (e.g., waveform 9324 and/or highamplitude “AH”). FIG. 11B illustrates an example where, in accordancewith a determination that the focus selector (e.g., cursor 9310) movesover an affordance displayed in a control region of an applicationwindow (e.g., icon 9312-a in control region 9304 of web browser 9302),the electronic device generates a tactile output (e.g., tactile output9322) that corresponds to affordances located in the control region(e.g., that feels different from a tactile output generated in responseto movement of the cursor over an affordance in a content region of anapplication window).

FIGS. 11C-11D illustrate various examples where the device detectsmovement 9320-b of contact 9318 on touch-sensitive surface 451 thatcorresponds to movement of cursor 9310 past the boundary of controlregion 9306 (e.g., below line 9308) and over navigation button 9314-1located in content region 9306 of web browser window 9302. In FIGS.11C-11D, the device (e.g., via tactile output generators 167) generatessecond tactile outputs 9326 or 9330 having a signature corresponding toan affordance (e.g., navigation button 9314-1) located in content region9306 (e.g., sawtooth waveform 9328 and/or a square waveform 9332 withlow amplitude “AL”). FIGS. 11C-11D illustrate examples where, inaccordance with a determination that the focus selector (e.g., cursor9310) moves over an affordance displayed in a control region of anapplication window (e.g., navigation button 9314-1 in control region9304 of web browser window 9302), the electronic device generates atactile output (e.g., tactile output 9326 or 9330) that corresponds toaffordances located in the control region (e.g., that feels differentfrom a tactile output generated in response to movement of the cursorover an affordance located in a control region of an applicationwindow).

FIGS. 11B and 11C illustrate an example where the second tactile output(e.g., tactile output 9326 in FIG. 11C) has substantially the samemaximum amplitude (e.g., high amplitude “AH”), but a substantiallydifferent movement profile (e.g., sawtooth waveform 9328), as the firsttactile output (e.g., tactile output 9322 in FIG. 11B having squarewaveform 9324). For example, the tactile feedback corresponding to themovement of cursor 9310 over navigation button 9314-1 located in contentregion 9306 is equally (or approximately) as strong as, but feelsdifferent from, the tactile feedback corresponding to the movement ofcursor 9310 over icon 9312-a located in control region 9304. Incontrast, FIGS. 11B and 11D illustrate an example where the secondtactile output (e.g., tactile output 9330 in FIG. 11D) has substantiallythe same movement profile (e.g., square waveform 9324), but a differentmaximum amplitude (e.g. low amplitude “AL”), as the first tactile output(e.g., tactile output 9322 in FIG. 11B having a high amplitude “AH”).For example, the tactile feedback corresponding to the movement ofcursor 9310 over navigation button 9314-1 located in content region 9306feels similar to, but is noticeably stronger or weaker than, the tactilefeedback corresponding to the movement of cursor 9310 over icon 9312-alocated in control region 9306.

As described above, tactile outputs are, optionally, generated foraffordances located in a control region and a content region of arespective application window (e.g., web browser window 9302). FIGS.11E-11G illustrate example waveforms of movement profiles for generatingthese tactile outputs. FIG. 11E illustrates a sawtooth waveform. FIG.11F illustrates a square waveform and FIG. 11G illustrates a squarewaveform that has a lower amplitude than the square waveform of FIG.11F. The high-amplitude square movement profile in FIG. 11F is,optionally, associated with movement of a focus selector over anaffordance located in a control region of an application window; thetactile output generated for moving over (e.g., scrolling over) anaffordance in a control region of an application window is, optionally,generated in accordance with a high-amplitude square movement profile.The low-amplitude square movement profile in FIG. 11G is, optionally,associated with movement of a focus selector over an affordance locatedin a content region of an application window; the tactile outputgenerated for moving over (e.g., scrolling over) an affordance in acontent region of an application window is, optionally, generated inaccordance with a low-amplitude square movement profile. The sawtoothmovement profile in FIG. 11E is, optionally, associated with movement ofa focus selector over an affordance located in a content region of anapplication window; the tactile output generated for selection of anaffordance in a content region of an application window is, optionally,generated in accordance with the sawtooth movement profile.

FIGS. 12A-12B are flow diagrams illustrating a method 9400 of providingfeedback when a focus selector moves over a user interface object inaccordance with some embodiments. The method 9400 is performed at anelectronic device (e.g., device 300, FIG. 3, or portable multifunctiondevice 100, FIG. 1A) with a display and a touch-sensitive surface. Insome embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 9400 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 9400 provides an intuitive way to providefeedback when a focus selector moves over a user interface object. Themethod reduces the cognitive burden on a user when detecting feedbackwhen a focus selector moves over a user interface object, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to detect feedback when a focusselector moves over a user interface object faster and more efficientlyconserves power and increases the time between battery charges.

In some embodiments, the device displays (9402) an application window(e.g., web browser window 9302 in FIGS. 11A-11D) that includes a controlregion (e.g., control region 9304 in FIGS. 11A-11D) and a content region(e.g., content region 9306 in FIGS. 11A-11D) distinct from the controlregion on a display (e.g., display 450 in FIGS. 11A-11D). In someembodiments, the control region includes (9404) a plurality ofaffordances for performing operations on content in the content region(e.g., icon 9312-a for saving browser based content, icon 9312-b fornavigating backwards in the browser's history and navigation bar 9312-cfor inputting a web address). In some embodiments, the plurality ofaffordances includes a toolbar of a web browser with buttons and dropdown menus that are content-independent. In some embodiments, theplurality of affordances in the control region includes (9406) multiplecontent-independent controls that are displayed in the control region ofthe application without regard to the content that is displayed in thecontent region. For example, application-specific controls that are notcontent-dependent, such as back/forward/reload/home buttons in a webbrowser and bold/italic/underline buttons in a word processingapplication.

In some embodiments, the content region displays (9408) content thatincludes one or more affordances (e.g., the hyperlinks shown in thewebpage in content region 9306 including navigation button 9314-1 inFIGS. 11A-11D) integrated into the content. For example, in someembodiments, the content is a webpage with a plurality of hyperlinks,text boxes, drop down menus and/or other selectable affordances that arecontent-dependent.

In some embodiments, while the device displays an application windowthat includes a control region and a content region distinct from thecontrol region, the device detects (9410) a contact (e.g., contact 9318in FIGS. 11A-11D) on a touch-sensitive surface (e.g., touch-sensitivesurface 451 in FIGS. 11A-11D). In some embodiments, the contact is afinger contact.

In some embodiments, while the device displays an application windowthat includes a control region and a content region distinct from thecontrol region, the device detects (9412) a gesture that includesmovement of the contact across the touch-sensitive surface (e.g.,movement 9320 of contact 9318 in FIGS. 11A-11D) that corresponds tomovement of a focus selector (e.g., cursor 9310 in FIGS. 11A-11D) on thedisplay across the application window. In some embodiments, the contactis the focus selector (e.g., when the device has a touch screen, thefocus selector is, optionally, contact 9318). In some embodiments, thecontact corresponds to a cursor or selection box that is displayed onthe display.

In some embodiments, in response (9414) to detecting the gesture: inaccordance with a determination that the gesture corresponds to movementof the focus selector over a first affordance in the control region(e.g., icon 9312-a in control region 9304 in FIG. 11B), the devicegenerates (9416) a first tactile output (e.g., tactile output 9322 inFIG. 11B) on the touch-sensitive surface (e.g., touch-sensitive surface451) that corresponds to movement of the focus selector over anaffordance in the control region.

In response (9414) to detecting the gesture: in accordance with adetermination that the gesture corresponds to movement of the focusselector over a second affordance in the content region (e.g.,navigation button 9314-1 in content region 9306 in FIGS. 11C-11D), thedevice generates (9418) a second tactile output (e.g., tactile output9326 in FIG. 11C or tactile output 9330 in FIG. 11D) on thetouch-sensitive surface (e.g., touch-sensitive surface 451) thatcorresponds to movement of the focus selector over an affordance in thecontent region, wherein the second tactile output is different from thefirst tactile output. For example, in some embodiments, a “detent” thatis generated on the touch-sensitive surface when a user moves acursor/contact over a button in a toolbar of an application feelsdifferent from a “detent” that is generated on the touch-sensitivesurface when a user moves a cursor/contact over a hyperlink in contentdisplayed in the application. In some embodiments, the first tactileoutput is more prominent (e.g., has a larger amplitude) than the secondtactile output. In some embodiments, the second tactile output is moreprominent (e.g., has a larger amplitude) than the first tactile output.

In some embodiments, the first tactile output is generated (9420) bymovement of the touch-sensitive surface that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface that includes a second dominant movementcomponent and the first dominant movement component and the seconddominant movement component have a substantially same amplitude (e.g.,high amplitude “AH” in FIGS. 11B-11C) and substantially differentmovement profiles (e.g., square waveform 9324 in FIGS. 11B and 11F andsawtooth waveform 9328 in FIGS. 11C and 11E). In some embodiments,movement of the touch-sensitive surface corresponds to an initialimpulse, ignoring any unintended resonance. In some embodiments, themovement profiles differ in their waveform shape (e.g., square, sine,squine, triangle or sawtooth waveform shape), waveform pulse widthand/or waveform pulse period (e.g., frequency). For example, asillustrated in FIGS. 11B-11C, a “detent” that is generated with thetouch-sensitive surface when a user moves a cursor/contact over a buttonin a toolbar of an application has a square waveform movement profile(e.g., waveform 9324 in FIGS. 11B and 11F), whereas a “detent” that isgenerated with the touch-sensitive surface when a user moves acursor/contact over a hyperlink in content displayed in the applicationhas a sawtooth waveform movement profile (e.g., waveform 9328 in FIGS.11C and 11E), or vice versa.

In some embodiments, the first tactile output is generated (9422) bymovement of the touch-sensitive surface that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface that includes a second dominant movementcomponent and the first dominant movement component and the seconddominant movement component have substantially a same movement profile(e.g., square waveforms 9324 in FIGS. 11B and 11F and square waveform inFIGS. 11D and 11G) and substantially different amplitudes (e.g., highamplitude “AH” in FIG. 11B and low amplitude “AL” in FIG. 11D). In someembodiments, movement of the touch-sensitive surface corresponds to aninitial impulse, ignoring any unintended resonance. For example, asillustrated in FIGS. 11B and 11D, a “detent” that is generated with thetouch-sensitive surface when a user moves a cursor/contact over a buttonin a toolbar of an application has less amplitude than a “detent” thatis generated with the touch-sensitive surface when a user moves acursor/contact over a hyperlink in content displayed in the application(e.g., high amplitude “AH” of tactile output 9322 in FIG. 11B is greaterthan low amplitude “AL” of tactile output 9330 in FIG. 11D), or viceversa.

It should be understood that the particular order in which theoperations in FIGS. 12A-12B have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in paragraph [0059]) are also applicable in an analogousmanner to method 9400 described above with respect to FIGS. 12A-12B. Forexample, the contacts, gestures, user interface objects, tactilesensations and focus selectors described above with reference to method9400 optionally have one or more of the characteristics of the contacts,gestures, user interface objects, tactile sensations and focus selectorsdescribed herein with reference to other methods described herein (e.g.,those listed in paragraph [0059]). For brevity, these details are notrepeated here.

In accordance with some embodiments, FIG. 13 shows a functional blockdiagram of an electronic device 9500 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 13 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 13, an electronic device 9500 includes a display unit9502 configured to display an application window that includes a controlregion and a content region distinct from the control region, atouch-sensitive surface unit 9504 configured to receive user contacts,optionally one or more sensor units 9506 configured to detect intensityof contacts with the touch-sensitive surface unit 9504; and a processingunit 9508 coupled to the display unit 9502, the touch-sensitive surfaceunit 9504 and optionally the one or more sensor units 9506. In someembodiments, the processing unit 9508 includes a display enabling unit9510, a detecting unit 9512 and a generating unit 9514.

In some embodiments, the processing unit 9508 is configured to enabledisplay (e.g., with the display enabling unit 9510) of an applicationwindow that includes a control region and a content region distinct fromthe control region on the display, where the control region includes aplurality of affordances for performing operations on content in thecontent region and the content region displays content that includes oneor more affordances integrated into the content. In some embodiments,the processing unit 9508 is further configured to detect a contact onthe touch-sensitive surface unit 9504 (e.g., with the detecting unit9512). In some embodiments, the processing unit 9508 is furtherconfigured to detect a gesture that includes movement of the contactacross the touch-sensitive surface unit 9504 (e.g., with the detectingunit 9512) that corresponds to movement of a focus selector on thedisplay unit 9502 across the application window; and in response todetecting the gesture: in accordance with a determination that thegesture corresponds to movement of the focus selector over a firstaffordance in the control region, the processing unit 9508 is configuredto generate a first tactile output on the touch-sensitive surface unit9504 (e.g., with the generating unit 9514) that corresponds to movementof the focus selector over an affordance in the control region; and inaccordance with a determination that the gesture corresponds to movementof the focus selector over a second affordance in the content region,the processing unit 9508 is configured to generate a second tactileoutput on the touch-sensitive surface unit 9504 (e.g., with thegenerating unit 9514) that corresponds to movement of the focus selectorover an affordance in the content region, where the second tactileoutput is different from the first tactile output.

In some embodiments, the plurality of affordances in the control regionincludes multiple content-independent controls that are displayed in thecontrol region of the application without regard to the content that isdisplayed in the content region.

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface unit 9504 that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface unit 9504 that includes a second dominantmovement component and the first dominant movement component and thesecond dominant movement component have a same amplitude and differentmovement profiles.

In some embodiments, the first tactile output is generated by movementof the touch-sensitive surface unit 9504 that includes a first dominantmovement component, the second tactile output is generated by movementof the touch-sensitive surface unit 9504 that includes a second dominantmovement component and the first dominant movement component and thesecond dominant movement component have a same movement profile anddifferent amplitudes.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 12A-12B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.13. For example, detection operations 9410 and 9412, determinationoperations 9416 and 9418 are, optionally, implemented by event sorter170, event recognizer 180 and event handler 190, respectively. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub-event, such as selection of an object on a user interface.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. In some embodiments, event handler 190 accesses arespective tactile output generator 167 to generate a tactile output ontouch-sensitive surface 451. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

Adjusting a Tactile Output Level in Accordance with an Adjustment of aVolume Level

Many electronic devices also change output levels of sensory propertiesof the device in response to the enablement of a setting or mode of thedevice. However, there are sometimes a large number of sensoryproperties to adjust and adjusting output levels of these sensoryproperties separately can be confusing and difficult for users. Theembodiments below provide a more convenient and intuitive user interfaceby adjusting a tactile output level of a device in tandem with anadjustment of a volume level of the device. Subsequently, the deviceprovides the adjusted tactile output level in response to detection of aplurality of inputs on a touch-sensitive surface. In some embodiments,the tactile output level changes in parallel with the volume level. Insome embodiments, the tactile output level changes inversely to thevolume level.

FIGS. 14A-14I illustrate exemplary user interfaces for adjusting atactile output level in accordance with an adjustment of a volume levelin accordance with some embodiments. The user interfaces in thesefigures are used to illustrate the processes described below, includingthe processes in FIGS. 15A-15C.

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 14A-14Iand FIGS. 15A-15C will be discussed with reference to display 450 and aseparate touch-sensitive surface 451, however analogous operations are,optionally, performed on a device with a touch-sensitive display system112.

FIG. 14A illustrates the device detecting a first plurality of inputs onthe touch-sensitive surface 451, including contacts 9602 and 9604. FIG.14A further illustrates volume level 9606 at a first level (e.g., L1).

FIG. 14B illustrates the device providing tactile feedback 9607 inaccordance with a tactile output level 9608 in response to detecting thefirst plurality of inputs (e.g., contacts 9602 and 9604). FIG. 14Bfurther illustrates volume level 9606 at the first level (e.g., L1).

FIG. 14C illustrates the volume level increasing by a respective amount(e.g., the difference between volume level 9606 and volume level 9610)from a first non-zero volume level to a second non-zero volume level inresponse to a request to adjust the volume of the device by therespective amount (e.g., from L1 to a level above L1, both of which arenon-zero volume levels in this example). FIG. 14C further illustratesadjusting the tactile output level (e.g., tactile output level 9608 inFIG. 14B) of the device by adjusting the amplitude of the respectivetactile output that corresponds to the respective input on thetouch-sensitive surface 451 in response to the request to adjust volumelevel 9606. FIG. 14C, for example, shows adjusted tactile output level9612 with an amplitude above A1 in contrast to the amplitude of tactileoutput level 9608 in FIG. 14B at A1, both of which are non-zero tactileoutput levels in this example.

In some embodiments, the request to adjust the volume of the device isreceived when a user depresses a physical button (e.g., a button forincreasing or decreasing volume, or a rocker switch for adjusting thevolume up or down depending on the direction in which it is depresses).In some embodiments, a request to adjust the volume of the device isreceived when the user makes a corresponding gesture on the touchsensitive surface 451, for example, when the user slides a displayedvolume indicator (displayed on the display 450) in a directioncorresponding to increased or decreased volume. In some embodiments,both modes of adjusting volume are available to the user.

FIG. 14C further illustrates adjusting the tactile output level (e.g.,tactile output level 9608 in FIG. 14B) of the device by adjusting themovement profile of the respective tactile output that corresponds tothe respective input on the touch-sensitive surface 451 in response tothe request to adjust volume level 9606. FIG. 14C, for example, showsadjusted tactile output level 9614 with a different waveform shape(e.g., triangular shape) in contrast to the waveform shape of tactileoutput level 9608 in FIG. 14B (e.g., rectangular shape).

FIG. 14C further illustrates adjusting the tactile output level (e.g.,tactile output level 9608 in FIG. 14B) of the device by adjusting theamplitude and the movement profile of the respective tactile output thatcorresponds to the respective input on the touch-sensitive surface 451in response to the request to adjust volume level 9606. FIG. 14C, forexample, shows adjusted tactile output level 9616 with both a greateramplitude (e.g., above A1) and a different waveform shape (e.g.,triangular shape) than tactile output level 9608 in FIG. 14B (e.g., withan amplitude at A1 and a rectangular shape).

FIG. 14D illustrates adjusting the tactile output level of the device byincreasing the tactile output level in accordance with a determinationthat adjusting the volume level by the respective amount includesincreasing the volume level. In this example, the volume level (e.g.,volume level 9606 in FIG. 14B) increases to a level above L1 (e.g.,volume level 9618). FIG. 14D further illustrates increasing the tactileoutput level 9608 to adjusted tactile output level 9620 in tandem withvolume level 9618.

FIG. 14E illustrates adjusting the tactile output level of the device bydecreasing the tactile output level in accordance with a determinationthat adjusting the volume level by the respective amount includesdecreasing the volume level. In this example, the volume level (e.g.,volume level 9606 in FIG. 14B) decreases to a level below L1 level(e.g., volume level 9622). FIG. 14E further illustrates decreasing thetactile output level 9608 to adjusted tactile output level 9624 (e.g., anon-zero level below A1) in tandem with volume level 9622.

FIG. 14F illustrates adjusting the tactile output level of the device bydecreasing the tactile output level in accordance with an increase inthe volume level by a respective amount. In this example, the volumelevel (e.g., volume level 9606 in FIG. 14B) increases to a level aboveL1 (e.g., volume level 9626). FIG. 14F further illustrates decreasingthe tactile output level 9608 to adjusted tactile output level 9628—theinverse of the change in volume level to volume level 9626.

FIG. 14G illustrates adjusting the tactile output level of the device byincreasing the tactile output level in accordance with a decrease in thevolume level by a respective amount. In this example, the volume level(e.g., volume level 9606 in FIG. 14B) decreases to a level below L1(e.g., volume level 9630). FIG. 14G further illustrates increasing thetactile output level 9608 to adjusted tactile output level 9632 aboveA1—the inverse of the change in volume level to volume level 9630.

FIG. 14H illustrates the device detecting a second plurality of inputs(e.g., contacts 9634 and 9636) on the touch-sensitive surface 451. Thedevice detects contacts 9634 and 9636, for example, subsequent toadjusting the tactile output level of the device (e.g., from the tactileoutput level 9608 in FIG. 14B to the tactile output level 9612 in FIG.14C).

FIG. 14I illustrates the device providing tactile feedback 9638 inaccordance with adjusted tactile output level 9612 and in response todetecting the second plurality of inputs (e.g., contacts 9634 and 9636)on the touch-sensitive surface 451.

FIGS. 15A-15C are flow diagrams illustrating a method 9700 of adjustinga tactile output level in accordance with an adjustment of a volumelevel in accordance with some embodiments. The method 9700 is performedat an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display and a touch-sensitivesurface. In some embodiments, the display is a touch screen display andthe touch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 9700 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 9700 provides an intuitive way to adjusta tactile output level in accordance with an adjustment of a volumelevel. The method reduces the cognitive burden on a user when adjustinga tactile output level in accordance with an adjustment of a volumelevel, thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, enabling a user to adjust a tactileoutput level in accordance with an adjustment of a volume level fasterand more efficiently conserves power and increases the time betweenbattery charges.

The device detects (9702) a first plurality of inputs on thetouch-sensitive surface. FIG. 14A, for example, shows a first pluralityof inputs (e.g., contacts 9602 and 9604) on the touch-sensitive surface451.

In response to detecting the first plurality of inputs, the deviceprovides (9704) tactile feedback in accordance with a tactile outputlevel of the device (e.g., the tactile output level corresponds to anaverage magnitude of tactile outputs, a magnitude of a reference tactileoutput generated by the device, or a magnitude of a maximum tactileoutput generated by the device). FIG. 14B, for example, shows the deviceproviding tactile feedback 9607 in accordance with tactile output level9608 and in response to detecting the first plurality of inputs (e.g.,contacts 9602 and 9604).

The device receives (9706) a request to adjust a volume level (e.g.,audio output level) of the device by a respective amount. FIG. 14C, forexample, shows the request to adjust the volume level of the device by arespective amount (e.g., the difference between volume level 9606 andvolume level 9610, both of which are non-zero volume levels in thisexample).

In response to the request (9708) to adjust the volume level, the deviceadjusts (9710) the volume level by the respective amount from a firstnon-zero volume level to a second non-zero volume level. FIG. 14C, forexample, shows increasing volume level 9606 (e.g., at level L1, anon-zero volume level) to volume level 9610 (e.g., at a level above L1,a non-zero volume level) in response to the request to adjust the volumelevel of the device.

In response to the request (9708) to adjust the volume level, the devicealso adjusts (9712) the tactile output level of the device in accordancewith the respective amount. FIG. 14C, for example, shows adjusting thetactile output level 9608 to adjusted tactile output level 9612 inresponse to the request to adjust the volume level of the device (e.g.,from volume level 9605 to volume level 9608).

In some embodiments, adjusting the tactile output level of the devicecomprises adjusting (9713) the tactile output level of the device, inaccordance with the respective amount, from a first non-zero tactileoutput level to a second non-zero tactile output level. FIG. 14C, forexample, shows adjusted tactile output level 9612 with an amplitudeabove A1 in contrast to the amplitude of tactile output level 9608 inFIG. 14B at A1, both of which are non-zero tactile output levels in thisexample.

In some embodiments, a respective tactile output that corresponds to arespective input on the touch-sensitive surface is generated (9714) bymovement of the touch-sensitive surface that includes a dominantmovement component that has a movement profile (e.g., a waveform shapesuch as square, sine, squine, sawtooth or triangle; and/or width/period)and an amplitude (e.g., movement corresponding to the initial impulse,ignoring any unintended resonance). In some embodiments, in response tothe request (9708) to adjust the volume level, adjusting the tactileoutput level of the device includes adjusting (9716) the amplitude ofthe respective tactile output that corresponds to the respective inputon the touch-sensitive surface (e.g., increasing or decreasing theamplitude of the initial impulse of the respective tactile output). FIG.14C, for example, shows adjusting the amplitude of tactile output level9608 in FIG. 14B (e.g., with an amplitude at A1) to produce adjustedoutput level 9612 (e.g., with an amplitude above A1), both of which arenon-zero tactile output levels in this example.

In some embodiments, a respective tactile output that corresponds to arespective input on the touch-sensitive surface is generated (9714) bymovement of the touch-sensitive surface that includes a dominantmovement component that has a movement profile (e.g., a waveform shapesuch as square, sine, squine, sawtooth or triangle; and/or width/period)and an amplitude (e.g., movement corresponding to the initial impulse,ignoring any unintended resonance). In some embodiments, in response tothe request (9708) to adjust the volume level, adjusting the tactileoutput level of the device includes adjusting (9718) the movementprofile of the respective tactile output that corresponds to therespective input on the touch-sensitive surface (e.g., increasing ordecreasing the width or shape of the initial impulse of the respectivetactile output). FIG. 14C, for example, shows adjusting the movementprofile of tactile output level 9608 in FIG. 14B (e.g., with arectangular waveform shape) to produce adjusted output level 9614 (e.g.,with a triangular waveform shape).

In some embodiments, in response to the request (9708) to adjust thevolume level, adjusting the tactile output level of the device includesadjusting (9718) the movement profile of the respective tactile outputthat corresponds to the respective input on the touch-sensitive surfaceand further includes adjusting (9720) the amplitude of the respectivetactile output that corresponds to the respective input on thetouch-sensitive surface. FIG. 14C, for example, shows adjusting both themovement profile and the amplitude of tactile output level 9608 in FIG.14B (e.g., with a rectangular waveform shape and an amplitude at A1) toproduce adjusted output level 9616 (e.g., with a triangular waveformshape and an amplitude above A1).

In some embodiments, in response to the request (9708) to adjust thevolume level, in accordance with a determination that adjusting thevolume level by the respective amount includes increasing the volumelevel, adjusting the tactile output level of the device includesincreasing (9722) the tactile output level (e.g., the tactile outputchanges in tandem with the audio output). For example, when the audiooutput level is increased by 50% the tactile output level is increasedby 50%. FIG. 14D, for example, shows volume level 9618 (e.g., a 50%increase from volume level 9606 in FIG. 14B) and adjusted tactile outputlevel 9620 (e.g., a 50% increase from tactile output level 9608 in FIG.14B).

In some embodiments, in response to the request (9708) to adjust thevolume level, in accordance with a determination that adjusting thevolume level by the respective amount includes decreasing the volumelevel, adjusting the tactile output level of the device includesdecreasing (9724) the tactile output level (e.g., the tactile outputchanges in tandem with the audio output). For example, when the audiooutput level is decreased by 50% the tactile output level is decreasedby 50%. FIG. 14E, for example, shows volume level 9622 (e.g., a 50%decrease from volume level 9606 in FIG. 14B) and adjusted tactile outputlevel 9624 (e.g., a 50% decrease from tactile output level 9608 in FIG.14B).

In some embodiments, in response to the request (9708) to adjust thevolume level, in accordance with a determination that adjusting thevolume level by the respective amount includes increasing the volumelevel, adjusting the tactile output level of the device includesdecreasing (9726) the tactile output level (e.g., the increased audiooutput is a replacement for the decreased tactile output). For example,when the audio output level is increased by 50% the tactile output levelis decreased by 50%. FIG. 14F, for example, shows volume level 9626(e.g., a 50% increase from volume level 9606 in FIG. 14B) and adjustedtactile output level 9628 (e.g., a 50% decrease from tactile outputlevel 9608 in FIG. 14B).

In some embodiments, in response to the request (9708) to adjust thevolume level, in accordance with a determination that adjusting thevolume level by the respective amount includes decreasing the volumelevel, adjusting the tactile output level of the device includesincreasing (9728) the tactile output level (e.g., the increased tactileoutput is a replacement for the decreased audio output). For example,when the audio output level is decreased by 50% the tactile output levelis increased by 50%. FIG. 14G, for example, shows volume level 9630(e.g., a 50% decrease from volume level 9606 in FIG. 14B) and adjustedtactile output level 9632 (e.g., a 50% increase from tactile outputlevel 9608 in FIG. 14B).

In some embodiments, after adjusting the tactile output level of thedevice, the device detects (9730) a second plurality of inputs on thetouch-sensitive surface. FIG. 14H, for example, shows the devicedetecting a second plurality of inputs (e.g., contacts 9634 and 9636) onthe touch-sensitive surface 451. The device detects contacts 9634 and9636 on the touch-sensitive surface 451, for example, subsequent toadjusting the tactile output level of the device (e.g., from tactileoutput level 9608 in FIG. 14B to adjusted tactile output level 9612 inFIG. 14C).

In some embodiments, in response to detecting the second plurality ofinputs on the touch-sensitive surface, the device provides (9732)tactile feedback in accordance with the adjusted tactile output level.FIG. 14I, for example, shows the device providing tactile feedback 9638in accordance with adjusted tactile output level 9612. The deviceprovides tactile feedback 9638, for example, subsequent to detecting thesecond plurality of inputs (e.g., contacts 9634 and 9636) on thetouch-sensitive surface 451.

It should be understood that the particular order in which theoperations in FIGS. 15A-15C have been described is merely exemplary andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein. Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in paragraph [0059]) are also applicable in an analogousmanner to method 9700 described above with respect to FIGS. 15A-15C. Forexample, the contacts (inputs), gestures and tactile sensationsdescribed above with reference to method 9700 optionally have one ormore of the characteristics of the contacts (inputs), gestures, andtactile sensations described herein with reference to other methodsdescribed herein (e.g., those listed in paragraph [0059]). For brevity,these details are not repeated here.

In accordance with some embodiments, FIG. 16 shows a functional blockdiagram of an electronic device 9800 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 16 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein 989898.

As shown in FIG. 16, an electronic device 9800 includes a display unit9802 configured to display information; a touch-sensitive surface unit9804 configured to receive inputs (e.g., contacts); a tactile feedbackunit 9806 configured to provide tactile feedback (e.g., generated bymovement of the touch-sensitive surface unit 9804); an audio unit 9808configured to produce an audio signal and an audio control signal inaccordance with at least a volume level (optionally includes an audiospeaker); and a processing unit 9810 coupled to the display unit 9802,the touch-sensitive surface unit 9804, the tactile feedback unit 9806,and the audio unit 9808. In some embodiments, processing unit 9810includes a detecting unit 9812, a providing unit 9814, a receiving unit9816, an adjusting unit 9818, and a determining unit 9820. Optionally,electronic device 9800 further includes one or more sensor units 9824configured to detect intensity of contacts with the touch-sensitivesurface unit 9804.

The processing unit 9810 is configured to: detect (e.g., with thedetecting unit 9812) a first plurality of inputs on the touch-sensitivesurface unit 9804; in response to detecting the first plurality ofinputs, provide (e.g., with the providing unit 9814) tactile feedbackvia tactile feedback unit 9806 in accordance with a tactile output levelof the device; and receive (e.g., with the receiving unit 9816) arequest to adjust a volume level of the device by a respective amount.The processing unit 9810 is further configured to, in response to therequest to adjust the volume level: adjust (e.g., with adjusting theunit 9818) the volume level by the respective amount; and adjust (e.g.,with the adjusting unit 9818) the tactile output level of the device inaccordance with the respective amount.

In some embodiments, a respective tactile output that corresponds to arespective input on the touch-sensitive surface unit 9804 is generatedby movement of the touch-sensitive surface unit 9804 that includes adominant movement component that has a movement profile and anamplitude; adjusting the tactile output level of the device includesadjusting (e.g., with the adjusting unit 9818) the amplitude of therespective tactile output that corresponds to the respective input onthe touch-sensitive surface unit 9804.

In some embodiments, a respective tactile output that corresponds to arespective input on the touch-sensitive surface unit 9804 is generatedby movement of the touch-sensitive surface unit 9804 that includes adominant movement component that has a movement profile and anamplitude; adjusting the tactile output level of the device includesadjusting (e.g., with the adjusting unit 9818) the movement profile ofthe respective tactile output that corresponds to the respective inputon the touch-sensitive surface unit 9804.

In some embodiments, the processing unit 9810 is configured to adjustthe tactile output level of the device by adjusting (e.g., with theadjusting unit 9818) the movement profile and the amplitude of therespective tactile output that corresponds to the respective input onthe touch-sensitive surface unit 9804.

In some embodiments, after adjusting (e.g., with the adjusting unit9818) the tactile output level of the device, the processing unit 9810is configured to detect (e.g., with the detecting unit 9812) a secondplurality of inputs on the touch-sensitive surface unit 9804; and inresponse to detecting the second plurality of inputs on thetouch-sensitive surface unit 9804, provide (e.g., with the providingunit 9814) tactile feedback via tactile feedback unit 9806 in accordancewith the adjusted tactile output level.

In some embodiments, the processing unit 9810 is configured to adjust(e.g., with the adjusting unit 9818) the output level of the device by:in accordance with a determination (e.g., with the determining unit9820) that adjusting the volume level by the respective amount includesincreasing the volume level, adjusting (e.g., with the adjusting unit9818) the tactile output level of the device includes increasing thetactile output level; and in accordance with a determination (e.g., withthe determining unit 9820) that adjusting the volume level by therespective amount includes decreasing the volume level, adjusting (e.g.,with the adjusting unit 9818) the tactile output level of the deviceincludes decreasing the tactile output level.

In some embodiments, the processing unit 9810 is configured to adjust(e.g., with the adjusting unit 9818) the output level of the device by:in accordance with a determination (e.g., with the determining unit9820) that adjusting the volume level by the respective amount includesincreasing the volume level, adjusting (e.g., with the adjusting unit9818) the tactile output level of the device includes decreasing thetactile output level; and in accordance with a determination (e.g., withthe determining unit 9820) that adjusting the volume level by therespective amount includes decreasing the volume level, adjusting (e.g.,with the adjusting unit 9818) the tactile output level of the deviceincludes increasing the tactile output level.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 15A-15C are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.16. For example, detecting operations 9702 and 9728, providingoperations 9704 and 9730, receiving operation 9706, adjusting operations9710-9712, and determining operations 9720-9726 are, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

Forgoing Generation of Tactile Output for a Multi-Contact Gesture

Many electronic devices provide a form of confirmation to a user inresponse to an event being triggered by a user action. For example, whena user clicks on an affordance (e.g., an icon button) corresponding torespective content (e.g., an electronic document, an image, or a video),an audio output is provided via a speaker to the user to confirm thatthe user is clicking on the affordance. Similarly, for example, after auser clicks on a hyperlink corresponding to a webpage, a web browserdisplays some form of visual confirmation (e.g., a semicircular arrowspinning in a clockwise manner or a spinning globe) indicating that thewebpage associated with the hyperlink is being loaded. However, thisconfirmation or feedback can be distracting or confusing to a user whenit occurs in response to inputs that do not correspond to the feedback.The embodiments described below provide a more convenient and intuitiveinterface by generating a tactile output in response to detecting agesture that includes a first number of contacts (e.g., one contact) andforging generating the tactile output if the gesture includes a secondnumber of contacts (e.g., two or more contacts).

Furthermore, in some embodiments, the device assigns less than all of aplurality of contacts to the gesture; thereby, excluding one or more ofthe plurality of contacts from the gesture in accordance with predefinedgesture criteria (e.g., shape, surface area, intensity, or chronologicalorder).

FIGS. 17A-17F illustrate exemplary user interfaces for generating atactile output for a gesture having a first number of contacts (e.g., asingle contact gesture) and forgoing generation of a tactile output fora gesture having a second number of contacts (e.g., a multi-contactgesture) in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIG. 18. FIGS. 17A-17F include intensitydiagrams that show the current intensity of the contact on thetouch-sensitive surface relative to a plurality of intensity thresholdsincluding a respective threshold (e.g., “IT_(L)”). In some embodiments,operations similar to those described below with reference to “IT_(L)”are performed with reference to a different intensity threshold (e.g.,“IT_(D)”).

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 450) and a separate touch-sensitive surface(e.g., touch-sensitive surface 451). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 167 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 17A-17Fand FIG. 18 will be discussed with reference to display 450 and aseparate touch-sensitive surface 451; however, analogous operations are,optionally, performed on a device with a touch-sensitive display system112 in response to detecting the contacts described in FIGS. 17A-17F onthe touch-sensitive display system 112 while displaying the userinterfaces shown in FIGS. 17A-17F on the touch-sensitive display system112; in such embodiments, the focus selector is, optionally: arespective contact, a representative point corresponding to a contact(e.g., a centroid of a respective contact or a point associated with arespective contact), or a centroid of two or more contacts detected onthe touch-sensitive display system 112, in place of cursor 9904.

FIG. 17A illustrates a user interface 9900 displayed on a display 450 ofan electronic device. In this example, the user interface 9900 isassociated with an application (e.g., a web browser), and the userinterface 9900 includes image 9902 and control icons 9903 (e.g., nextimage button 9903-1 and previous image button 9903-2, associated with asequence of images of the week). FIG. 17A further illustrates a contact9906 detected on touch-sensitive surface 451 and a displayedrepresentation of a focus selector (e.g., cursor 9904) corresponding tocontact 9906. In this example, cursor 9904 is located over next imagebutton 9903-1. FIG. 17A illustrates the intensity of contact 9906between IT₀ and IT_(L).

FIGS. 17A-17B illustrates an example of detecting, on thetouch-sensitive surface 451, a gesture that includes an increase ofintensity of a contact 9906 above a respective intensity threshold(e.g., “IT_(L)”). In this example, the intensity of contact 9906increases (e.g., from below IT_(L) in FIG. 17A to above IT_(L) in FIG.17B) above the respective intensity threshold (e.g., “IT_(L)”).

FIG. 17B illustrates an example of generating a tactile output (e.g.,tactile output 9910) on the touch sensitive 451. In this example, thedevice generates tactile output 9910 on the touch sensitive 451 inresponse to detecting the gesture (e.g., the increase of intensity ofcontact 9906 above IT_(L)) and in accordance a determination that thegesture includes a first number of contacts. In some embodiments, thefirst number of contacts is one contact. FIGS. 17A-17B illustratedetecting the gesture including one contact (e.g., contact 9906). FIG.17B further illustrates displaying image 9908 on display 450 in responseto the press input (e.g., the increase in intensity of contact 9906above IT_(L)) while cursor 9904 is over next image button 9903-1, whichrelates to the next image in the sequence of images of the week.

FIG. 17C illustrates detecting two contacts (e.g., contacts 9912 and9914) on the touch-sensitive surface 451. In this example, contact 9912corresponds to cursor 9904 (e.g., contact 9912 was detected prior tocontact 9914). FIG. 17C further illustrates the intensities of contacts9912 and 9914 between IT₀ and IT_(L).

FIGS. 17C-17D illustrate an example of detecting, on the touch-sensitivesurface 451, a gesture that includes an increase of intensity of contact9912 above a respective intensity threshold (e.g., “IT_(L)”). In thisexample, the intensity of contact 9912 increases (e.g., from belowIT_(L) in FIG. 17C to above IT_(L) in FIG. 17D) above the respectiveintensity threshold (e.g., “IT_(L)”).

FIGS. 17C-17D further illustrate a multi-touch pinch (zooming out)gesture. In this example, the multi-touch pinch gesture includes contact9912 moving from location 9912-a in FIG. 17C to location 9912-b in FIG.17D and contact 9914 moving from location 9914-a in FIG. 17C to location9914-b in FIG. 17D (e.g., contacts 9912 and 9914 are moving towards eachother while remaining contact with the touch-sensitive surface 451).FIGS. 17C-17D illustrate zooming out from, or reducing the size of,image 9902 and control icons 9903 (e.g., image 9902 and control icons9903 are displayed at a smaller size in FIG. 17D, in contrast to FIG.17C) in response to the multi-touch pinch gesture.

FIG. 17D illustrates an example of forgoing generating a tactile outputon the touch sensitive 451. In this example, the device forgoesgenerating the tactile output (e.g., tactile output 9910 in FIG. 17B isnot generated) on the touch sensitive 451 in response to detecting thegesture (e.g., the movement of contacts 9912 and 9914 toward each otherthat includes the increase of intensity of contact 9912 above IT_(L))and in accordance with a determination that the gesture includes asecond number of contacts (e.g., contacts 9912 and 9914). In someembodiments, the second number of contacts is two or more contacts.FIGS. 17C-17D illustrate detecting the gesture including two contacts(e.g., contacts 9912 and 9914).

FIG. 17E illustrates detecting a plurality of contacts (e.g., contacts9918 and 9920) on the touch-sensitive surface 451. In this example,contact 9918 corresponds to cursor 9904 (e.g., contact 9918 was detectedprior to contact 9920), and the intensities of contacts 9918 and 9920are between IT₀ and IT_(L).

FIG. 17E further illustrates assigning one or more of the plurality ofcontacts, comprising less than all of the plurality of contacts, to thegesture in accordance with predefined gesture criteria. In this example,contact 9918 is assigned to the gesture in accordance with predefinedgesture criteria, but contact 9920 (e.g., representing a portion of auser's palm on touch-sensitive surface 451) is not assigned to thegesture (e.g., contact 9920 is not in accordance with predefined gesturecriteria including shape and surface area, these predefined gesturecriteria sometimes include accidental input rejection criteria such aspalm rejection criteria that enable the device to ignore accidentalcontacts on the touch-sensitive surface such as a contact formed by thepalm of a user's hand).

FIGS. 17E-17F illustrate an example of detecting, on the touch-sensitivesurface 451, a gesture that includes an increase of intensity of acontact (e.g., contact 9918) above a respective intensity threshold(e.g., “IT_(L)”). In this example, the intensity of contact 9918increases (e.g., from a level below IT_(L) in FIG. 17E to a level aboveIT_(L) in FIG. 17F) above the respective intensity threshold (e.g.,“IT_(L)”).

FIG. 17F illustrates an example of generating a tactile output (e.g.,tactile output 9910) on the touch sensitive 451. In this example, thedevice generates tactile output 9910 on the touch sensitive 451 inresponse to detecting the gesture (e.g., the increase of intensity ofcontact 9918 above IT_(L)) and in accordance with a determination thatthe gesture includes a first number of contacts (e.g., one contact, inthis example contact 9918, excluding contact 9920). FIG. 17F furtherillustrates displaying image 9908 on display 450 in response to thepress input (e.g., the increase in intensity of contact 9918 aboveIT_(L)) while cursor 9904 is over next image button 9903-1, whichrelates to the next image in the sequence of images of the week). Insome embodiments, the next image button 9903-1 is activated in responseto an increase in intensity of contact 9918 above IT_(L) (e.g., thedown-stroke of a press input). In some embodiments, the next imagebutton 9903-1 is activated in response to a subsequent decrease inintensity of contact 9918 below IT_(L) (e.g., the up-stroke of a pressinput).

FIG. 18 is a flow diagram illustrating a method 10000 of generating atactile output for a gesture having a first number of contacts (e.g., asingle contact gesture) and forgoing generation of a tactile output fora gesture having a second number of contacts (e.g., a multi-contactgesture) in accordance with some embodiments. The method 10000 isperformed at an electronic device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1A) with a display and a touch-sensitivesurface. In some embodiments, the display is a touch screen display andthe touch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 10000 are, optionally, combined and/or the order of someoperations is, optionally, changed.

As described below, the method 10000 provides an intuitive way togenerate a tactile output for a gesture having a first number ofcontacts and forgo generation of a tactile output for a gesture having asecond number of contacts. The method reduces the cognitive burden on auser when generating a tactile output for a gesture having a firstnumber of contacts and forgoing generation of a tactile output for agesture having a second number of contacts, thereby creating a moreefficient human-machine interface. For battery-operated electronicdevices, enabling a user to generate a tactile output for a gesturehaving a first number of contacts and forgo generation of a tactileoutput for a gesture having a second number of contacts conserves powerand increases the time between battery charges.

The device detects (10002), on a touch-sensitive surface, a gesture thatincludes an increase of intensity of a contact above a respectiveintensity threshold. FIGS. 17A-17B, for example, show a gesture thatincludes an increase of intensity of contact 9906 (e.g., from belowIT_(L) in FIG. 17A to above IT_(L) in FIG. 17B) above a respectiveintensity threshold (e.g., “IT_(L)”) on the touch-sensitive surface 451.

In some embodiments, the gesture includes (10004) a press input detectedon the touch-sensitive surface while a focus selector is over a controlicon (e.g., a button) displayed on the display. FIGS. 17A-17B, forexample, show a press a press input detected on the touch-sensitivesurface 451 (e.g., the increase in the intensity of contact 9906 frombelow IT_(L) in FIG. 17A to above IT_(L) in FIG. 17B) while a focusselector (e.g., cursor 9904) is over a control icon (e.g., next imagebutton 9903-1) displayed on the display 450.

In some embodiments, the respective intensity threshold is (10006) anactivation threshold and the tactile output provides a confirmation tothe user that the activation threshold has been met. For example, atactile output confirming to the user that an operation has beenperformed, or a tactile output confirming to the user that an operationwill be performed upon detecting an end of the gesture, such as liftoffof the contact. FIG. 17B, for example, shows tactile output 9910 ontouch-sensitive surface 451 providing confirmation to the user that theactivation threshold has been met (e.g., the respective intensitythreshold—IT_(L)).

In response to detecting the gesture (10008) and in accordance with adetermination that the gesture includes a first number of contacts, thedevice generates (10010) a tactile output on the touch-sensitivesurface. FIG. 17B, for example, shows tactile output 9910 generated ontouch-sensitive surface 451 in response to detecting the gesture (e.g.,an increase in the intensity of contact 9906 above IT_(L)) and inaccordance with a determination that the gesture includes a first numberof contacts (e.g., contact 9906).

In some embodiments, the first number of contacts is (10012) one contact(e.g., the tactile output is generated when the gesture is asingle-contact press input). FIGS. 17A-17B, for example, show thegesture including one contact (e.g., contact 9906).

In some embodiments, the tactile output is (10014) a tactile output thatcorresponds to the increase of intensity of the contact above therespective intensity threshold. For example, the tactile output that isgenerated when the gesture includes a first number of contacts (and isnot generated when the gesture includes a second number of contacts) isa tactile output that corresponds to the increase of intensity of acontact above a respective threshold (e.g., “IT_(L)”). In someembodiments, the tactile output is a simulation of a “mouse click”tactile output that is generated by the device when a contact exceeds a“down click” intensity threshold (e.g., “IT_(L)”) and the gesture isperformed with a single contact (e.g., the user performs a press inputwith a single contact). FIG. 17B, for example, shows tactile output 9910corresponding to the increase of intensity of contact 9906 above therespective intensity threshold (e.g., “IT_(L)”).

In some embodiments, the tactile output is (10016) a predefined tactileoutput (e.g., to simulate a “mouse click” sensation corresponding todepressing a physical actuator on a mouse or trackpad) that is generatedwhen the user performs one of a set of predefined single-contact userinterface object interaction operations in the user interface. Forexample, the tactile output corresponds to a “mouse click” sensation,where the “mouse click” sensation is provided in response to selectionof user interface objects when the user is using the touch-sensitivesurface as a single-contact trackpad (e.g., rather than a multi-contactgesture input area).

In response to detecting the gesture and in accordance with adetermination that the gesture includes a second number of contacts, thedevice forgoes (10018) generating the tactile output on thetouch-sensitive surface. FIG. 17D, for example, shows the deviceforgoing generation of the tactile output on the touch-sensitive surface451 (e.g., tactile output 9910 in FIG. 17B is not generated) in responseto detecting the gesture (e.g., an increase in the intensity of contact9912 from below IT_(L) in FIG. 17C to above IT_(L) in FIG. 17D) and inaccordance with a determination that the gesture includes a secondnumber of contacts (e.g., contacts 9912 and 9914). In some embodiments,the tactile output is not generated when the gesture is performed withmultiple contacts (e.g., the user performs a multi-contact gesture suchas a pinch or depinch gesture). FIGS. 17C-17D, for example, show amulti-touch pinch gesture on touch-sensitive surface 451.

In some embodiments, the second number of contacts is (10020) two ormore contacts (e.g., the tactile output is not generated when thegesture is a multi-contact pinch/depinch gesture). FIGS. 17C-17D, forexample, show the pinch gesture including two or more contacts (e.g.,contacts 9912 and 9914).

In some embodiments, the device detects (10022) a plurality of contactson the touch-sensitive surface and assigns one or more of the pluralityof contacts, comprising less than all of the plurality of contacts, tothe first gesture in accordance with predefined gesture criteria. Insome embodiments, one or more simultaneously detected contacts areexcluded from the gesture (e.g., the device ignores palm contact oraccidental contacts on the touch-sensitive surface). In someembodiments, predefined gesture criteria include: a shape of the one ormore of the plurality of contacts, a surface area of the one or more ofthe plurality of contacts, an intensity of the one or more of theplurality of contacts, a predefined or chronological order of theplurality of contacts, or any combination thereof.

FIGS. 17E-17F, for example, show the detection of a plurality ofcontacts (e.g., contacts 9918 and 9920) on the touch-sensitive surface451. FIGS. 17E-17F, for example, also show the assignment of one of theplurality of contacts (e.g., contact 9918), comprising less than all ofthe plurality of contacts, to the gesture in accordance with predefinedgesture criteria. For example, the shape and surface area of contact9918 (e.g., circular and approximately the surface area of a user'sfinger tip) are in accordance with the predefined gesture criteria, butthe shape and surface area of contact 9920 (e.g., oblong and having asurface area greater than a predefined maximum surface area for a touchcontact) are not in accordance with predefined gesture criteria.

It should be understood that the particular order in which theoperations in FIG. 18 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,those listed in paragraph [0059]) are also applicable in an analogousmanner to method 10000 described above with respect to FIG. 18. Forexample, the contacts, gestures, user interface objects, intensitythresholds, and focus selectors described above with reference to method10000 optionally have one or more of the characteristics of thecontacts, gestures, user interface objects, intensity thresholds, andfocus selectors described herein with reference to other methodsdescribed herein (e.g., those listed in paragraph [0059]). For brevity,these details are not repeated here.

In accordance with some embodiments, FIG. 19 shows a functional blockdiagram of an electronic device 10100 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 19 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 19, an electronic device 10100 includes: a display unit10102 configured to display a graphical user interface; atouch-sensitive surface unit 10104 configured to receive contacts; oneor more sensor units 10106 configured to detect intensity of contactswith the touch-sensitive surface unit 10104; a tactile output unit 10108configured to generate a tactile output (e.g., generated by movement ofthe touch-sensitive surface unit 10104); and a processing unit 10110coupled to the display unit 10102, the touch-sensitive surface unit10104, the one or more sensor units 10106, and the tactile output unit10108. In some embodiments, the processing unit 10110 includes adetecting unit 10112, a determining unit 10114, a generating unit 10116,and an assigning unit 10118.

The processing unit 10110 is configured to: detect (e.g., with thedetecting unit 10112), on the touch-sensitive surface unit 10104, agesture that includes an increase of intensity of a contact above arespective intensity threshold. The processing unit 10110 is furtherconfigured to, in response to detecting the gesture: in accordance witha determination (e.g., with the determining unit 10114) that the gestureincludes a first number of contacts, generate (e.g., with the generatingunit 10116) a tactile output via the tactile output unit 10108 on thetouch-sensitive surface unit 10104; and in accordance with adetermination (e.g., with the determining unit 10114) that the gestureincludes a second number of contacts different from the first number,forgo generating the tactile output on the touch-sensitive surface unit10104.

In some embodiments, the tactile output is a tactile output thatcorresponds to the increase of intensity of the contact above therespective intensity threshold.

In some embodiments, the tactile output is a predefined tactile outputthat is generated via the tactile output unit 10108 when the userperforms one of a set of predefined single-contact user interface objectinteraction operations in the user interface.

In some embodiments, the first number of contacts is one contact, andthe second number of contacts is two or more contacts.

In some embodiments, the respective intensity threshold is an activationthreshold and the tactile output provides a confirmation to the userthat the activation threshold has been met.

In some embodiments, the gesture includes a press input detected (e.g.,with the detecting unit 10112) on the touch-sensitive surface unit 10104while a focus selector is over a control icon displayed on the displayunit 10102.

In some embodiments, the processing unit 10110 is further configured to:detect (e.g., with the detecting unit 10112) a plurality of contacts onthe touch-sensitive surface unit 10104; and assign (e.g., with theassigning unit 10118) one or more of the plurality of contacts,comprising less than all of the plurality of contacts, to the gesture inaccordance with predefined gesture criteria.

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIG. 18 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.19. For example, detecting operations 10002 and 10022, determiningoperations 10010 and 10018, and generating operation 10010 are,optionally, implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

It should be understood that the particular order in which theoperations have been described above is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that the various processes separatelydescribed herein (e.g., those listed in paragraph [0059]) can becombined with each other in different arrangements. For example, thecontacts, user interface objects, tactile sensations, intensitythresholds, and/or focus selectors described above with reference to anyone of the various processes separately described herein (e.g., thoselisted in paragraph [0059]) optionally have one or more of thecharacteristics of the contacts, gestures, user interface objects,tactile sensations, intensity thresholds, and focus selectors describedherein with reference to one or more of the other methods describedherein (e.g., those listed in paragraph [0059]). For brevity, all of thevarious possible combinations are not specifically enumerated here, butit should be understood that the claims described above may be combinedin any way that is not precluded by mutually exclusive claim features.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the various described embodiments to the precise forms disclosed.Many modifications and variations are possible in view of the aboveteachings. The embodiments were chosen and described in order to bestexplain the principles of the various described embodiments and theirpractical applications, to thereby enable others skilled in the art tobest utilize the various described embodiments with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by an electronic device with adisplay, a touch-sensitive surface and one or more sensors to detectintensity of contacts with the touch-sensitive surface, cause the deviceto: detect, on the touch-sensitive surface, a gesture that includes anincrease of intensity of a contact above a respective intensitythreshold; and in response to detecting the gesture: in accordance witha determination that the gesture includes a first number of contacts,generate a tactile output on the touch-sensitive surface; and inaccordance with a determination that the gesture includes a secondnumber of contacts different from the first number, forgo generating thetactile output on the touch-sensitive surface.
 2. The computer readablestorage medium of claim 1, wherein the tactile output is a tactileoutput that corresponds to the increase of intensity of the contactabove the respective intensity threshold.
 3. The computer readablestorage medium of claim 1, wherein: the tactile output is a predefinedtactile output that is generated when the user performs one of a set ofpredefined single-contact user interface object interaction operationsin the user interface.
 4. The computer readable storage medium of claim1, wherein: the first number of contacts is one contact; and the secondnumber of contacts is two or more contacts.
 5. The computer readablestorage medium of claim 1, wherein the respective intensity threshold isan activation threshold and the tactile output provides a confirmationto the user that the activation threshold has been met.
 6. The computerreadable storage medium of claim 1, wherein the gesture includes a pressinput detected on the touch-sensitive surface while a focus selector isover a control icon displayed on the display.
 7. The computer readablestorage medium of claim 1, including instructions which cause the deviceto: detect a plurality of contacts on the touch-sensitive surface; andassign one or more of the plurality of contacts, comprising less thanall of the plurality of contacts, to the gesture in accordance withpredefined gesture criteria.
 8. An electronic device, comprising: adisplay; a touch-sensitive surface; one or more sensors to detectintensity of contacts with the touch-sensitive surface; one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: detecting, on the touch-sensitive surface, a gesture that includesan increase of intensity of a contact above a respective intensitythreshold; and in response to detecting the gesture: in accordance witha determination that the gesture includes a first number of contacts,generating a tactile output on the touch-sensitive surface; and inaccordance with a determination that the gesture includes a secondnumber of contacts different from the first number, forgoing generatingthe tactile output on the touch-sensitive surface.
 9. A method,comprising: at an electronic device with a display and a touch-sensitivesurface, wherein the device includes one or more sensors to detectintensity of contacts with the touch-sensitive surface: detecting, onthe touch-sensitive surface, a gesture that includes an increase ofintensity of a contact above a respective intensity threshold; and inresponse to detecting the gesture: in accordance with a determinationthat the gesture includes a first number of contacts, generating atactile output on the touch-sensitive surface; and in accordance with adetermination that the gesture includes a second number of contactsdifferent from the first number, forgoing generating the tactile outputon the touch-sensitive surface.